AI for HubSpot.
Coco reads your HubSpot CRM, drafts the work it would propose, and gates every external write on your approval. Reads are free; sends, field updates, and sequence enrollments need a yes the first time through.
Coco connects to HubSpot over OAuth, reads contacts, deals, companies, and engagement, and proposes work against that context — research, drafts, follow-ups, hygiene.
Reading is free. Writing — sending an email, updating a field, enrolling a contact in a sequence — gates on your approval at the start. After you've approved a workflow a few times and trust the pattern, you can graduate it to autonomous execution inside your guardrails. HubSpot's native AI (Breeze) works in parallel; Coco is the layer that runs across your stack, with HubSpot as one tool among several.
What Coco does inside HubSpot today.
HubSpot is where your forecast lives — deal stages, lifecycle states, owner assignments, and the activity log your whole team reads. That makes it the right CRM for Coco to connect to first: not as a data warehouse to mine, but as the record of truth Coco reasons against when it drafts, enriches, and flags. Below, the six capabilities are listed in order of how often they run, followed by the scope matrix that shows exactly what each one costs you in permissions and approval clicks, and nine plays that combine them into repeatable workflows.
- 01Read contacts, companies, deals.Free
Names, titles, lifecycle stage, deal amount, close date, owner, last activity, custom properties, lists, and sequences.
- 02Watch HubSpot lists.Free
Coco can sit on a HubSpot list and pick up new entries as they arrive: a "Design partner candidates" list, or "Stale Q2 deals."
- 03Draft work against records.Free draft
First-touch emails, follow-ups, meeting briefs, sequence enrollments, contact-field updates — all prepared and shown before any external action.
- 04Send 1:1 email from your inbox.Approval
The send happens via your connected Gmail or Outlook, signed by you. Coco logs the activity back into HubSpot on the contact record.
- 05Update contact and deal fields.Approval
Lifecycle stage, deal stage, custom properties, owner, notes, tasks — visible as a diff before you approve, with the prior value preserved in the activity log.
- 06Enroll contacts in sequences.Approval
Coco can shortlist contacts for a sequence and queue them, but the enrollment itself — the moment the sequence starts running on a person — only happens after you click Approve.
The scope you'd actually grant.
On the left, the screen Coco shows you at install: the OAuth scopes it requests from HubSpot, in plain English. On the right, what each capability costs you in approval clicks. Every write action carries a note explaining why the gate is there.
Connect Coco to HubSpot
Coco is requesting access to your HubSpot portal. Reads are toggled on by default; writes ship gated and run only after your approval.
- ReadRead contacts, companies, deals
So Coco can see the records and properties it's reasoning about.
- ReadRead engagement & activity
Email opens, meeting bookings, notes: context Coco uses to know what to do next.
- ReadRead lists, sequences, properties
So Coco can watch a list as it grows and target the right sequence templates.
- GatedUpdate contact & deal properties
For field changes Coco proposes. Each change shown as a diff before it lands.
- GatedCreate notes, tasks, activity
For logging Coco-drafted work back to the record so the rest of your team sees it.
- GatedEnroll in sequences
For starting outreach sequences. Coco queues; you approve to start the run.
The send happens from your address, signed by you. Coco shows the recipient and full body before you approve. We treat sends like signing a letter.
Field changes are visible to every rep on the record. Coco shows the prior and new value side by side; approve overwrites a column at a time.
A stage move is a forecast event. Coco never moves a deal silently, even one suggested by an obvious activity pattern.
Sequences run autonomously once started. Coco only enrolls after you've reviewed the contact list and the first step of the sequence.
Lighter-weight than a field overwrite, but visible to your team on the record. Approve in batch with the full text shown.
Five minutes, read-only at the end.
Four steps. Standard HubSpot OAuth. After the last step Coco is connected and watching, but no external action will fire until you approve the first workflow.
Open Coco · Settings · Integrations.
Pick HubSpot from the integration list. Coco shows the scope screen you saw above; nothing has been requested from HubSpot yet.
Sign in to HubSpot.
Standard HubSpot OAuth in a new tab. If you manage multiple portals (sandbox, production, multi-hub), pick the portals you want Coco to see: one or all.
Review and grant scopes.
HubSpot's permission screen lists the scopes Coco asks for, mapped one-to-one to the rows you saw. Granting writes here doesn't give Coco the right to send; Coco still gates every write on your approval inside its own UI.
Coco syncs and shows you what it sees.
First sync of contacts, deals, lists, and properties: typically under a minute for portals under ~20k contacts. Coco surfaces a read-only summary of what it found before proposing the first workflow.
Find design partners, sourced from a HubSpot list.
The same shape every Coco-on-HubSpot workflow follows. Here's the one most teams run first: design-partner search, off a HubSpot list.
Find design partners, sourced from a HubSpot list.
You build a HubSpot list called Design partner candidates with the firmographics you can filter on. Coco watches the list, runs a deep research pass on each contact, attaches the brief to the contact record, drafts a first-touch in your Gmail, and queues each contact for a design-partner intro sequence, pending your approval. About 25 cr to shortlist 5–10 candidates, plus 4–6 cr per draft.
- Read list Design partner candidatesHubSpot · Contacts → ListsFree
- Read engagement on each contactHubSpot · Activity timelineFree
- Draft first-touch in your GmailCoco · queued, not sentDraft
- Attach research brief as a noteHubSpot · NotesApproval
- Set lifecycle stage to Design partnerHubSpot · Contact propertyApproval
- Enroll in Design partner introHubSpot · SequenceApproval
Nine plays that run on HubSpot.
Each one uses the same approval-gated pattern above. Reveal more as you read — three at a time.
Find design partners.
Five ranked accounts in your Gmail drafts, with research and sources attached. Sourced from a HubSpot list.
Research accounts in pipeline.
Pick a deal stage. Coco runs a depth pass per account and attaches a brief to the HubSpot record before your next call.
Clean CRM data.
Dedup, enrich missing properties, fix routing — proposed as diffs against the contact and company records.
Draft post-meeting follow-ups.
After a Calendly meeting lands on the calendar, Coco queues a draft and a CRM update for your approval.
Prep before sales meetings.
One-page brief lands in your inbox the morning of each call — context, last touchpoints, three questions to ask.
Re-engage stalled deals.
Coco watches deals past your silence threshold, drafts a re-engagement note, and queues a stage-update task.
Enrich missing contact fields.
Find titles, roles, mutual connections, and decision-maker maps for contacts you already have — no enrichment-tool seat.
Forecast hygiene.
Flag deals with stage, activity, and close-date mismatches. Coco proposes a single-screen fix-list for your weekly review.
Build a list from one seed.
Hand Coco one customer; get back a HubSpot list of look-alikes with the research attached as notes on each.
Working alongside HubSpot Breeze.
HubSpot ships its own AI, Breeze (formerly ChatSpot). It drafts well inside HubSpot's own UI. Here's where Coco adds what Breeze doesn't cover.
- Breeze is in-HubSpot. Coco is across your stack.Breeze reasons inside HubSpot's data, with HubSpot's UI. Coco connects HubSpot to Gmail, Slack, Calendly, Apollo, LinkedIn — and runs the workflow across them. If a play needs to touch HubSpot and Gmail and the open web, that's Coco.
- Breeze drafts in-context. Coco drafts and gates the execution.Breeze is excellent at drafting an email in HubSpot's composer or summarising a record. Coco draws the same drafts but treats every external send, field overwrite, or sequence start as a separate decision you make in one place.
- Breeze is bundled. Coco is a separate seat.If you're already paying for a HubSpot tier that includes Breeze, run both. Many teams do: Breeze for in-record summarisation, Coco for the cross-tool workflow. Coco doesn't try to replace what Breeze does well inside HubSpot's UI.
Questions about the integration.
01Which HubSpot tiers does Coco work with?
Starter, Pro, and Enterprise across Sales, Service, and Marketing Hub. Some scopes (sequences, custom properties) require Pro or higher on HubSpot's side; Coco gracefully degrades — capabilities that need a scope you don't have are hidden, not failed.
02Can Coco run on a sandbox before touching production?
Yes. At the OAuth step you pick which portals Coco can see. A common pattern is sandbox-only for the first week, then add the production portal once you've watched the workflow run end-to-end with approval clicks.
03Does Coco see deals it shouldn't see?
Coco inherits your HubSpot role and team permissions. A rep who can't see another team's deals in HubSpot won't see them through Coco either. Workspace-level Coco actions respect the connecting user's HubSpot ACL.
04Can I roll back a change Coco made?
Every Coco-made write is logged on the HubSpot record with the prior value, the new value, and the workflow that proposed it. Reverting is a one-click action in Coco; in HubSpot it appears as an activity-log entry your team can audit.
05What happens if HubSpot rate-limits Coco?
Coco respects HubSpot's API quotas and backs off automatically. For large operations (a 5k-record enrichment pass) Coco queues and runs incrementally; you see progress in the workflow view rather than a failed batch.
06How does Coco store HubSpot data?
Coco reads on demand and caches only what's needed for the active workflow: typically minutes to hours, not days. Sensitive properties stay in HubSpot; Coco doesn't build a shadow CRM. Full data-handling notes live in our security overview.
07Can I narrow Coco's scope after I've connected?
Yes — from HubSpot's Settings · Integrations panel, or from Coco. Narrowing a scope disables only the capabilities that need it; the rest keep running. Revoking entirely disconnects Coco from your portal in one click.
Connect HubSpot, stay read-only. Write when ready.
Five minutes of OAuth. Watch Coco propose one workflow against your live data. Approve it, reject it, or let it sit. Nothing leaves your account until you click Approve.