Coco
Register for Beta

Integrations

Coco does the work inside the tools you already use. Connect a tool, grant the scopes you choose, and Coco can read context, draft work, and execute actions with your approval at every external step.

Coco connects to the tools you already use: HubSpot, Salesforce, Gmail, Google Calendar, Apollo, LinkedIn, Clay, Outreach, Slack, Notion, Calendly, and ZoomInfo. For each connection, Coco can read for context, draft work in that tool's language and format, and execute actions with your approval at every external step. You control the scopes you grant. You can revoke any connection at any time. Coco doesn't make you migrate or rebuild. It does the work inside the stack you have. The full list with what Coco does in each tool is below.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

How Coco connects to a tool

The connection flow is built to be done in under a minute per tool. You pick the integration from the integrations page inside Coco, grant the scopes you want Coco to have, and the connection validates before going live. For OAuth-based tools (HubSpot, Salesforce, Gmail, Google Calendar, Slack, Notion, Calendly, LinkedIn), the flow is the standard scope-grant dialog. For API-key tools (Apollo, ZoomInfo, Clay), the flow is paste the key, click validate, watch the validation run.

Take the Apollo connection as a concrete example. The flow: open the integrations page, click Apollo, paste your APOLLO_API_KEY, click connect. Coco runs a validation call against Apollo's API and fails fast on bad keys with a structured error. You see what went wrong (invalid credentials, expired key, scope insufficient) rather than a generic "connection failed." Once the key validates, the connection establishes. Safe lookup tools (read-only contact and company searches) become available immediately. Enrichment, list-building, sequence enrollment, and bulk operations stay behind the approval gate until you authorize specific workflows.

Per-user encrypted credential storage holds your keys. Each user's keys live in their own Fernet-encrypted store inside the per-user container. Decryption happens only when a tool call needs the key. Team-owned credentials (for shared workflows) live in environment variables on the backend rather than the per-user store. See the security page for the full key-handling architecture.

The split between what's available pre-approval (reads, lookups, drafting) and what requires approval (writes, sends, spends, bulk operations) is consistent across every integration. Low-risk surfaces work as soon as the connection is live; anything that ships an action or spends meaningfully waits for your explicit go-ahead.

The integrations Coco supports today

Grouped by what they're for.

CRM

HubSpot. Coco reads contacts, companies, and deals to build context for outreach, follow-ups, and meeting prep. Drafts follow-up emails grounded in HubSpot context. Proposes CRM writes (lifecycle stage updates, missing-field fills, deduplication merges) — all gated by approval. Stale-deal flagging surfaces deals that have been silent past your threshold and queues drafted re-engagement messages for your review. The integration is the foundation for the CRM hygiene workflow and the deal-reactivation sweep. About 1–3 credits per record touched. See the HubSpot integration →

Salesforce. Same surface as HubSpot, mapped to Salesforce objects (Accounts, Contacts, Opportunities, Leads). Coco reads for context, drafts work, and proposes writes to Standard or Custom Objects. Approval-gated on every write. Lead routing audit, opportunity stage hygiene, and contact enrichment all run inside Salesforce against the data you already have. Works alongside Einstein — Coco operates as cross-tool execution where Einstein stays in-platform. See the Salesforce integration →

Email and calendar

Gmail. Coco drafts outbound emails and follow-up replies in your voice, grounded in the context it pulled from research and CRM. Drafts queue in your Gmail Drafts folder; sends are approval-gated. Coco can read for context with the inbox scope you grant — most teams grant a label-scoped read so Coco sees only the conversations relevant to a specific workflow. About 4–6 credits per drafted outreach email. See the Gmail integration →

Google Calendar. Coco reads upcoming meetings to build pre-meeting briefs (about 8 credits per brief), drafts scheduling messages, and proposes calendar writes (new event, attendee changes, reschedules) gated by approval. The integration ties into the meeting-prep workflow and the post-meeting follow-up flow. See the Google Calendar integration →

Data and enrichment

Apollo. The first orchestration-grade integration Coco shipped (v0.5.2.0). Safe lookup tools (contact and company searches, basic enrichment reads) work pre-approval as soon as your API key validates. Enrichment writes, list-building, sequence enrollment, and bulk operations require approval. Coco coordinates Apollo data with HubSpot/Outreach/Gmail in single multi-tool workflows — the design-partner research pipeline runs against Apollo data, lands enriched contacts in HubSpot, and queues drafts in Gmail. About 1–2 credits per record enriched (plus Apollo's own API metering). See the Apollo integration →

Clay. Data enrichment integration. Coco pulls Clay-enriched data into workflows that need richer context than what Apollo or ZoomInfo provide. The orchestration model: Coco proposes the plan; Clay (or Claygent, where you're using it) runs the enrichment Coco asks for; Coco handles the work that surrounds the enrichment — drafting, queuing, CRM hygiene. About 1–2 credits per record on the Coco side (plus Clay's own credit consumption). See the Clay integration →

ZoomInfo. Contact and company lookups. Safe read tools work pre-approval. Bulk operations are approval-gated. Coco uses ZoomInfo for contact discovery when Apollo's data is sparse for a specific segment, and for cross-checking signals across multiple sources before a high-stakes outreach run. See the ZoomInfo integration →

Engagement

Outreach. Coco reads sequence state to surface conversations that need a next move, drafts replies grounded in the sequence context, and queues next-steps for your approval. Sends through Outreach remain gated. The orchestration model: Coco coordinates the Outreach Voyager AI inside cross-team workflows — meeting prep, post-sequence follow-up, CRM hygiene on contacts Outreach touched all live outside Outreach itself. About 3–5 credits per drafted reply. See the Outreach integration →

LinkedIn. Draft LinkedIn outreach (connection requests, intro messages, follow-ups), identify mutual connections to surface warm paths, and queue messages for your review. Sends are approval-gated; Coco does not post to LinkedIn without your explicit approval. About 2–4 credits per message drafted. See the LinkedIn integration →

Comms and docs

Slack. Coco surfaces activity to channels you've connected — daily roll-ups of what ran, what's pending approval, what's queued. Coco can post agent updates and approval requests to a Slack channel (approval-gated; the post itself requires your sign-off on the message content). The integration is most useful for teams who want their GTM operations chatter centralized in Slack. See the Slack integration →

Notion. Read for context (project pages, meeting notes, playbook docs), write meeting summaries and next-step notes into the pages and databases you've connected. Approval-gated on writes. Coco can pull from your Notion knowledge base to ground outreach drafts in your team's own framing — useful for B2B teams whose product positioning lives in Notion rather than in CRM fields. See the Notion integration →

Scheduling

Calendly. Read availability and event types, propose new meeting links, and surface booked meetings for the prep-brief workflow. Coco doesn't reschedule or cancel without your approval. The integration ties into the meeting-prep flow: when a Calendly booking lands, Coco can kick off the pre-meeting brief automatically (inside the guardrails you've set for that workflow). See the Calendly integration →

Orchestration integrations

Beyond the standard set, Coco has orchestration integrations with three AI tools that have their own narrow specialties. Coco doesn't replace these tools. It coordinates them inside broader GTM workflows. 11x (Alice) for autonomous outbound volume: Coco supplies research-rich ICPs into Alice's campaigns and handles meeting prep, CRM hygiene, and follow-through on Alice's booked meetings. Artisan (Ava) for AI BDR work: same pattern as 11x, with Coco wrapping the workflow that surrounds the volume engine. Salesloft for cadence-based execution: Coco reads Salesloft Cadence state and Rhythm AI signals, drafts cross-tool work that lives outside Salesloft (post-cadence follow-up in Gmail, CRM hygiene on Cadence-touched contacts, meeting prep on Cadence-booked calls). The orchestration angle: Coco is the layer that turns specialized AI tools into a coordinated GTM motion instead of a stack of islands.

What "with approval" means per integration

The approval-gate model is consistent across integrations, but the specific gated actions differ by tool. A quick reference:

  • Email tools (Gmail). Drafts queue freely. Sends are gated. Reading for context with the scope you grant is free.
  • CRM (HubSpot, Salesforce). Reads are free. Writes (new contacts, field updates, deal stage moves, contact deletions) are gated. Stale-deal flagging and hygiene proposals queue for approval before anything writes.
  • Apollo, ZoomInfo, Clay. Read-only lookups work pre-approval. Enrichment writes, list-building, sequence enrollment, and bulk operations are gated. Third-party API costs (Apollo/ZoomInfo/Clay credits) come out of your Coco credit balance at unit cost.
  • Outreach. Sequence state reads are free. Drafts are free. Sends and sequence enrollment changes are gated.
  • LinkedIn. Drafts are free. Sends, connection requests, and posts are gated.
  • Slack, Notion. Reads (for context) are free. Writes (channel posts, page writes, database row writes) are gated.
  • Calendar (Google Calendar, Calendly). Reads are free. Writes (new events, reschedules, cancellations) are gated.

The pattern: reads and drafts are free of the gate; anything that ships an action, spends credits meaningfully, or changes state in an external tool stays behind it. See the approval-gate detail → for what happens at the gate in practice.

Tools we're adding next

The current integration set covers the most-requested GTM stacks. The roadmap is driven by customer pull — new integrations ship when there's repeat demand from teams whose specific stack we don't yet cover. Candidates currently in the queue based on customer asks: marketing automation platforms (Marketo, Pardot/Account Engagement), data warehouses (Snowflake, BigQuery for reverse ETL into Coco workflows), customer success tools (Gainsight, ChurnZero), and SDR-tool extensions beyond the current orchestration set.

If your stack includes a tool we don't cover, tell us. New integrations are usually shippable within a few weeks once we've seen the demand justify the engineering work.

What if my tool isn't on the list

Two paths. The first: Coco can often work with an adjacent tool. If you're on Pipedrive instead of HubSpot, Coco can still pull contact context from Apollo-enriched data and draft work in Gmail — you lose the deep CRM hygiene workflow but keep most of the value. If you're on Outlook instead of Gmail, the same patterns apply through the standard Outlook scope. If you're on Salesloft instead of Outreach, the orchestration integration with Salesloft covers the sequence-coordination use case.

The second path: request the integration. Coco's integration set is built around demand, not around an arbitrary "supported tools" list. New integrations ship quickly once the demand is real.

Stack architecture — how Coco fits

A short architectural piece for the RevOps reader. Coco doesn't replace your CRM, your email tool, your enrichment vendor, or your engagement platform. It uses them.

The integration model: your data stays in the source tool. HubSpot is still the system of record for contacts. Gmail is still where your inbox lives. Apollo is still where the enrichment data sits. Coco operates on that data — pulls it for context, drafts work against it, proposes writes that go back into the source tool with your approval. There's no Coco-side data store that mirrors your CRM. There's no migration step. There's no parallel system to keep in sync.

This is a deliberate design choice. The pitch from a lot of AI-first sales platforms is "consolidate onto our system and the AI works better." Coco's pitch is the opposite: your stack is fine; the AI works inside it. If you've spent years configuring HubSpot the way your team works — custom properties, lifecycle stages, deal-stage logic, workflow triggers — the last thing you want is to throw all that configuration away. Coco makes the configuration you already have do more work.

The cost implication of the architecture: there's no per-integration fee. All the integrations listed above are part of every tier, including Hobby. See the pricing page for what's included where.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Frequently asked questions

Can I connect multiple instances of the same tool?

Currently one connection per tool per account. If your team operates in multiple HubSpot portals or multiple Salesforce orgs, talk to us about Team tier — multi-instance support is on the near roadmap for teams with that pattern.

How are API keys stored?

Fernet-encrypted at rest, per-user, in the encrypted key store inside your isolated runtime container. Decryption happens only when a tool call needs the key, inside your container. Team-owned credentials (for shared workflows) live in environment variables on the backend rather than the per-user store. Rotation is supported without losing the configured workflows — updating a key takes about a minute.

What scopes do you ask for?

The minimum needed for each integration's listed capabilities. Read scopes for context-building. Specific write scopes only for the workflows that need them. The connection flow shows the requested scopes before you grant them, and you can grant a subset if you want Coco running in a more restricted mode. Each integration page documents the exact scopes Coco asks for.

Can I limit Coco to read-only?

Yes — grant only read scopes on the integration and Coco runs in research-and-draft mode. It can pull context, draft outreach, propose CRM writes, and queue work in the activity feed — but the gated actions (sends, writes, bulk operations) won't have the permission to execute even if you approve them. Many teams evaluate this way for the first two weeks.

What happens to my workflows if I disconnect a tool?

Workflows pause. Queued state is preserved. When you reconnect the tool, the workflows resume from where they paused. There's no data loss; nothing in inconsistent state. The audit trail captures the disconnection event and the resumption.

Are there per-integration fees?

No. All integrations are part of every tier, including the free Hobby tier. There's no per-tool monthly tax on top of credit pricing. Third-party API costs (Apollo credits, ZoomInfo lookups, Clay enrichment) come out of your Coco credit balance at unit cost — no platform markup.

What if my tool offers its own AI features — does Coco conflict?

No. Coco operates as a separate co-worker that uses your tool's API. Your tool's native AI features (HubSpot Breeze, Salesforce Einstein, Apollo's AI Copilot, Outreach Voyager) run independently in their own platforms. Coco's job is the cross-tool execution that the native AI features aren't positioned to handle — the work that lives upstream, downstream, and around the tool-specific AI rather than inside it. Most teams running Coco alongside a native AI feature find they're complementary.

Get started

Pick one tool from your stack. Connect it. Hand Coco one concrete workflow that touches that tool — a CRM hygiene sweep, a research-plus-draft pipeline, a follow-up audit. Watch how the approval gate behaves on real data. See whether the output earns the next integration.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Or book a walkthrough → if you'd rather see Coco running across multiple integrations first.