Coco + Salesforce

Connect Salesforce once and Coco operates inside it as your AI co-worker. Coco reads Accounts, Contacts, Opportunities, and Leads freely for context. It drafts follow-ups, proposes enrichment updates with source attribution, flags stale opportunities, identifies duplicates, and prepares pre-meeting briefs grounded in Salesforce data. Every write action — updating a record, advancing an opportunity stage, sending email through Salesforce, logging activity — gates on your approval at the start. Once an approved workflow is proven, you can let Coco run it autonomously inside the guardrails you set. About 1-2 credits per record read; 1-3 credits per record write.

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

What Coco does with Salesforce today

Coco operates against the standard Salesforce API surface — Accounts, Contacts, Opportunities, Leads, plus custom objects where your org has them. No managed package to install. The connection is OAuth and the data flow is real-time.

Reads Accounts, Contacts, Opportunities, and Leads for context. Free of approval. When you ask Coco for a brief on an Opportunity, it pulls the Opportunity record, the related Account, the associated Contacts, the open Tasks and Events, and the last 90 days of Activities. About 1-2 credits per record touched on the read side.

Drafts follow-ups grounded in Salesforce data. When a Contact replies, when an Opportunity sits silent past your threshold, when a stage advances, Coco drafts the next-step email from the actual Activity history and Opportunity state. Drafts queue for your review. Send is gated. See automate follow-ups → for the full workflow.

Proposes enrichment with source attribution. Missing email on a Contact, blank Industry on an Account, empty Annual Revenue field — Coco surfaces a fillable proposal with the source it pulled from (LinkedIn, Apollo, Clay, ZoomInfo, public web). You approve before anything writes to Salesforce. About 1-2 credits per enrichment proposal.

Flags stale Opportunities. Coco watches your pipeline and surfaces Opportunities that have gone silent past whatever threshold you set. Each stale Opportunity arrives as a drafted re-engagement message queued for review. See reactivate stale deals →.

Identifies likely duplicates. Two Contacts with the same email under different Accounts, an Account under two spellings, a Lead that should already be a Contact — Coco proposes the merge or convert with the diff visible before the write. See clean CRM data →.

Prepares pre-meeting briefs from Salesforce data. The morning of a meeting, Coco assembles a brief from the Contact's record, the related Opportunity, recent Activities, and any associated notes or attached files. About 8 credits per brief.

Custom objects work via the API. If your org has custom objects (e.g., Renewals, Onboarding Stages, Partner Records), Coco reads them the same way it reads standard objects and can propose writes gated by the same approval model.

Updates fields, creates Leads/Contacts, advances Opportunity stages, logs Activities, sends email through Salesforce, converts Leads. All approval-gated. Coco proposes; you approve; the write lands.

How to connect

The connection flow is OAuth-based.

1. Go to /app/integrations.
2. Pick Salesforce.
3. Run the OAuth flow. Grant the scopes you want enabled — read scopes for context, specific write scopes only for workflows you've turned on.
4. Coco confirms the connection and tests read access.
5. Approve the first workflow (typically follow-up drafting or stale-opportunity flagging).

Coco works with Professional, Enterprise, and Unlimited editions. Group and Essentials editions have API limitations that block most workflows. See the security model → for what gets logged and how scope revocation works.

Approval gates by action type

Once you've approved a recurring pattern a few times, you can graduate that specific workflow to autonomous execution inside the rules you set. Send still gates per draft by default.

Workflows that use Salesforce

Salesforce is the source of truth for most of Coco's GTM workflows when it's your CRM. The ones that lean hardest on it:

• Clean CRM data → — duplicates, missing fields, stale records, broken Lead-to-Contact conversions.
• Enrich contacts → — fill missing fields with source-attributed proposals.
• Automate follow-ups → — drafts queued after reply, silence, or stage change.
• Reactivate stale deals → — pipeline silence sweep with drafted re-engagement.

Each workflow uses Salesforce as the source of truth for record state and as the destination for approved writes.

Working alongside Salesforce Einstein

Salesforce has its own AI layer — Einstein. Honest framing: Einstein and Coco solve different problems and coexist cleanly.

Einstein lives inside Salesforce. It scores Leads, suggests next-best actions on Opportunities, surfaces forecasts and pipeline insights, drafts content inside Salesforce's UI. It's the in-platform AI for Salesforce-native work.

Coco is the cross-tool co-worker. The drafted follow-up that lives in your Gmail Drafts folder, the pre-meeting brief that pulls from Salesforce plus your calendar plus your Notion playbook, the marketing handoff that touches Salesforce plus Slack plus your ads platform — that's outside Einstein's scope. It's the work that doesn't fit inside one tool.

Many teams run both. Einstein for in-platform scoring and surfacing. Coco for the cross-tool execution that turns those signals into work the team can actually act on. See why Coco's wedge sits in the cross-tool layer →.

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

Frequently asked questions

Which Salesforce editions does Coco work with?

Professional, Enterprise, and Unlimited. Group and Essentials editions have API limitations that block most workflows. If you're on Group or Essentials, contact us before connecting.

Will Coco overwrite my data?

No write action lands without your approval at the start. Coco proposes; you review the diff; you approve. Once a recurring pattern has proven out, you can authorize it to run inside specific guardrails — but the default is approval per write.

Does Coco work with custom Salesforce objects?

Yes. If a custom object is accessible via the API (which is most), Coco reads it the same way it reads standard objects. Writes to custom objects use the same approval gate as standard objects.

How does Coco compare to Salesforce Einstein?

Different layers. Einstein is the in-platform AI inside Salesforce — Lead scoring, next-best actions, Salesforce-native drafting. Coco is the cross-tool co-worker that operates across Salesforce and your other tools — Gmail, Calendar, Slack, Notion, your enrichment vendors. They coexist; Einstein stays inside Salesforce, Coco handles the work that crosses tools.

What scopes does Coco request?

Minimum needed for enabled workflows. Read scopes for context; specific write scopes only when you've turned on a workflow that requires them. You can revoke any scope at any time and Coco's affected workflows pause until you grant it again.

Is the integration depth the same as HubSpot?

Largely yes — the same workflow set runs against both. The two CRMs map cleanly: HubSpot Deals correspond to Salesforce Opportunities, Companies to Accounts, Contacts to Contacts. A handful of HubSpot-specific UI flows (notably HubSpot Email through the platform's UI) have Salesforce equivalents but a slightly different API surface. The user-visible workflow experience is the same.

Get started

If your Salesforce has the usual mess — stale Opportunities, missing fields, Leads that should be Contacts, follow-ups that never shipped — the connection takes a couple minutes and starts surfacing work the same day.

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

Or book a walkthrough → if you'd rather see the Salesforce workflow in action first.