Coco + Apollo

Apollo is supported as of Coco v0.5.2.0. Connect it from /app/integrations by pasting your APOLLO_API_KEY — Coco validates the key fail-fast (bad keys return a structured invalid-credentials response before anything is saved). Once connected, Coco can run Apollo's safe lookup tools immediately without re-approval; enrichment, writes, email sends, sequence enrollment, and bulk operations remain behind the approval gate. The key is encrypted at rest per user. About 1-2 credits per record lookup; about 30+ credits per bulk enrichment run.

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

What Coco does with Apollo today

The Apollo integration shipped in Coco v0.5.2.0 with a clean capability split: safe lookups are free after connection; anything that costs Apollo credits, mutates state, or sends through Apollo is approval-gated.

Lookup contacts and companies (free post-connect). Once the API key is connected and validated, Coco can run Apollo's lookup tools — find a contact by email, find a company by domain, search for people by title and company — without re-approving each call. About 1-2 credits per lookup on Coco's side. These tools don't consume Apollo's enrichment credits.

Propose enrichment (approval-gated). When Coco identifies that a contact record is missing fields, it can propose an Apollo enrichment with the data preview visible. You approve before Apollo's credits are spent and before the enriched data writes back to your CRM. See enrich contacts →.

Build target lists from Apollo's database. When you ask Coco for "Series A SaaS founders in NYC with a CRM problem," it can search Apollo's database against your criteria and return a shortlist. The list itself is a free output. Any subsequent enrichment of the shortlisted records, or any sequence enrollment, gates on approval. See find design partners → and research accounts →.

Draft outreach grounded in Apollo data. Once you've approved an enriched list, Coco can draft first-touch outreach using the Apollo data as input. Drafts queue in your Gmail Drafts folder. About 4-6 credits per drafted outreach. See draft cold outreach →.

Enroll contacts into Apollo sequences (approval-gated). Coco can propose sequence enrollment for a vetted list. You approve the enrollment; Apollo runs the sequence; Coco watches reply state. The enrollment itself is approval-gated; subsequent send operations through Apollo follow Apollo's own delivery posture.

Bulk operations (approval-gated). Bulk enrichment, bulk contact creation, bulk sequence enrollment — each operation surfaces a preview with the count and estimated Apollo credit cost. You approve before the bulk runs. About 30+ credits per bulk enrichment run on Coco's side, plus the Apollo credits consumed.

How to connect (the v0.5.2.0 flow)

Apollo connects via API key. The flow is explicit.

1. Go to /app/integrations.
2. Pick Apollo. The Apollo brand mark renders in the connect sheet.
3. Paste your APOLLO_API_KEY. Get it from Apollo's settings — Account Settings → Integrations → API.
4. Coco validates the key fail-fast. If the key is bad, you get a structured invalid-credentials response before anything is saved. No silent failure, no half-connected state.
5. On valid keys, Coco confirms the connection and the key is Fernet-encrypted at rest per user.
6. Approve the first workflow you want to enable (typically a lookup or research run).

The key is scoped per-user; team members each connect their own Apollo. See the security model → for how credentials are stored and revoked.

Approval gates by action type

The capability split in v0.5.2.0 is deliberately conservative on writes and generous on safe reads.

Once you've approved a recurring pattern — say, "auto-enrich any new HubSpot contact that comes in from a target ICP list" — you can graduate that specific workflow to autonomous execution inside the rules you set. Bulk operations and sends still gate per run by default.

Workflows that use Apollo

Apollo is connected to most of Coco's pipeline-finding and research workflows. The ones that lean hardest:

• Find design partners → — target search with Apollo as the database surface.
• Research accounts → — Apollo data as one input alongside public web, LinkedIn, and your CRM.
• Enrich contacts → — Apollo as one of several enrichment sources, with source attribution preserved.
• Draft cold outreach → — outreach drafted against Apollo-sourced context.

Working alongside Apollo AI Copilot

Apollo has its own AI layer — Apollo AI Copilot, sometimes called Apollo AI Sales Engineer. Honest framing: Apollo's AI and Coco solve different problems and coexist.

Apollo AI Copilot lives inside Apollo. It scores prospects against your ICP, generates AI-personalized email drafts inside Apollo, suggests sequence improvements based on engagement data, and surfaces buying signals from Apollo's intent data. It's the in-platform AI for Apollo-native work.

Coco is the cross-tool co-worker. The drafted outreach that lands in your Gmail Drafts folder (not in Apollo's send queue), the pre-meeting brief that pulls from Apollo plus your CRM plus your calendar, the post-meeting follow-up that touches Apollo plus Gmail plus Salesforce — that's outside Apollo's scope. It's the work that crosses tools.

Many teams run both. Apollo AI for in-platform prospecting and sequence optimization. Coco for the cross-tool work that surrounds it — research depth, CRM hygiene on Apollo-touched contacts, meeting prep, follow-through. 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

Do I need an Apollo subscription?

Yes. Coco uses your Apollo API key, which requires an Apollo plan that includes API access. Most Apollo paid tiers include it. Free and lower-tier plans may not — check Apollo's current plan matrix before connecting.

Is my Apollo API key safe?

Yes. The key is Fernet-encrypted at rest per user. It's scoped to your account in Coco and never shared across users or teams. You can revoke at any time from /app/integrations, which both deletes the key from Coco's storage and pauses any workflows that depend on it.

What if my key is bad?

Fail-fast. When you paste a key that's malformed, expired, or doesn't authenticate against Apollo's API, Coco returns a structured invalid-credentials response and refuses to save the connection. You don't end up in a half-connected state where some workflows quietly fail later.

Can Coco enroll contacts into Apollo sequences?

Yes — approval-gated. Coco proposes the enrollment with the contact list and the destination sequence visible. You approve; Apollo runs the sequence under Apollo's own delivery infrastructure. Coco watches reply state and surfaces results back into your other tools (CRM, follow-up workflows).

Does Coco use Apollo for bulk email sends?

Yes — approval-gated, with explicit warnings on the preview. Bulk send through Apollo follows Apollo's own deliverability posture. Coco's approval-first model is meant to keep brand and deliverability risk visible; the responsibility for sending hygiene still sits with you and Apollo's send infrastructure.

Get started

The Apollo integration is shipped today. If you have an Apollo plan with API access, the connection takes under a minute and the first lookup runs immediately. The free tier of Coco includes enough credits to evaluate Apollo workflows properly before any spend.

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

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