Apollo + Claude Code Integration via Deepline

What This Integration Does

Deepline connects your Apollo account to Claude Code via a native CLI skill. Once connected, Claude Code can enrich contacts via Apollo's People Match endpoint, combine Apollo with other providers in a waterfall, and push results to sequencers — all from slash commands or plain English.

No MCP servers. No browser automation. Deepline is a CLI that Claude Code calls directly, the same way it calls git or curl. Direct API calls use 5-10x fewer tokens than equivalent MCP operations.

In Claude Code, an agent can say: /deepline enrich leads.csv --with apollo_people_match and Deepline handles everything — auth, rate limiting, retries, and structured output.

Quick Start

Three steps to enrich contacts with Apollo from Claude Code:

curl -s "https://code.deepline.com//api/v2/cli/install" | bash

deepline config set APOLLO_API_KEY your_key

deepline enrich leads.csv --with 'email=apollo_people_match:{"first_name":"{{First Name}}","last_name":"{{Last Name}}","organization_name":"{{Company}}"}'

Why Use Deepline vs Calling Apollo's API Directly

You could write custom code to call Apollo's People Match endpoint. Here is why teams use Deepline instead:

What Apollo Data You Can Access via Deepline

Deepline exposes Apollo's full People Match API. Every data point Apollo returns is available as a column in your output CSV:

Apollo People Match Endpoint

Under the hood, Deepline calls Apollo's POST /v1/people/match endpoint. Here is the request structure Deepline constructs from your CSV columns:

// Apollo People Match — what Deepline sends per row
POST https://api.apollo.io/v1/people/match
{
  "first_name": "Jane",
  "last_name": "Doe",
  "organization_name": "Acme Corp",
  "email": "jane@acme.com"  // optional — improves match rate
}

// Response includes:
// email, phone, title, seniority, linkedin_url,
// organization.name, organization.industry,
// organization.estimated_num_employees, ...

You never write this code. Deepline maps your CSV headers to the request fields and flattens the response into CSV columns automatically.

Apollo in a Waterfall

Apollo alone typically covers 70-80% of B2B emails. By adding Crustdata and PDL as fallback providers, you can push coverage to 85%+. Deepline handles this with a single flag:

# Apollo first, Crustdata second, PDL third — stop at first hit
deepline enrich leads.csv \
  --with-waterfall email \
  --providers apollo,crustdata,pdl

# Full waterfall with email validation and AI scoring
deepline enrich leads.csv \
  --with-waterfall email \
  --providers apollo,crustdata,pdl \
  --with 'verify=leadmagic_email_validation:{"email":"{{email}}"}' \
  --with 'score=call_ai:{"prompt":"Score this lead against our ICP: {{verify}}","json_mode":true}'

The waterfall stops at the first provider that returns a result for each row. You only pay for the match that succeeds. If Apollo finds an email on the first try, Crustdata and PDL are never called for that row. Learn more about waterfall enrichment.

Using Apollo with Claude Code in Plain English

You don't need to memorize CLI flags. After installing Deepline, just tell Claude Code what you want in plain English. It reads the skill docs and calls the right Deepline commands automatically.

deepline enrich leads.csv --with apollo_people_match

deepline enrich leads.csv --with-waterfall email --providers apollo,pdl

deepline enrich leads.csv --with apollo_people_match \
  --with 'verify=leadmagic_email_validation:{"email":"{{email}}"}' \
  --with 'score=call_ai:{"prompt":"Score this lead...","json_mode":true}'

Trusted by GTM teams

Frequently Asked Questions

Related

• What is waterfall enrichment?
• Deepline vs Apollo — when to use each
• Install Deepline CLI