Documentation · Workflows
How to Push Apollo People into a HeyReach LinkedIn Campaign with Claude Code
Connect Apollo and HeyReach in Deepline, describe the ICP, and Claude filters for LinkedIn URLs + normalizes them + pushes to the HeyReach campaign. Respects LinkedIn's 50-100 invites/day cap automatically.
What you need
Step-by-step
- 1
Install Deepline
One command installs the Deepline CLI and registers a workspace. Takes about 30 seconds. You only do this once per machine.
curl -s "https://code.deepline.com/api/v2/cli/install" | bash deepline auth register - 2
Connect Apollo in the Deepline dashboard
In the Deepline dashboard, click Integrations → Apollo → paste your API key from app.apollo.io/settings/integrations/api. Deepline stores it encrypted and uses it for every Apollo call from this point on.
- 3
Connect HeyReach in the Deepline dashboard
In the Deepline dashboard, click Integrations → HeyReach → paste your API key from HeyReach Settings → API Keys. Deepline lists LinkedIn campaigns and enforces daily invite caps automatically.
- 4
Chat with Claude
Open Claude Code and describe the workflow in plain English. Deepline handles the tool calls, waterfall routing, rate limits, auth refresh, and dedup. An example prompt for this pair:
> From Apollo, find Directors and VPs of Engineering at US SaaS companies with 51-500 employees. Keep only rows with a linkedin_url. Normalize the URL to the canonical format. Add them to HeyReach campaign "Eng Leader LinkedIn Outbound" with apollo_id and apollo_seniority as custom fields. - 5
Deploy as a workflow
Once Claude's one-off run looks right, type "Deploy this as a workflow" and tell it the schedule. Deepline wraps the exact prompt + tool chain as a recurring workflow with run history, billing, and alerting in the dashboard.
> Deploy this as a workflow that runs every weekday morning at 8am.
Cost math
For 1,000 leads: $2.50
~0.25 credits per person added. Apollo enrichment + LinkedIn-URL filtering (~60% of Apollo rows have a usable URL). HeyReach write is free. Deepline's credit pricing is pay-as-you-go — see code.deepline.com/docs/pricing for current rates.
Why do it in Claude Code
Waterfall routing by default
Deepline tries the cheapest provider first and only falls back if it misses. For Apollo workflows, this means email enrichment stops at the first valid hit — you don't pay for the second and third provider unless you need to.
Deploy the exact prompt as a schedule
Once the one-off run looks right, "Deploy this as a workflow" wraps the same prompt + tool chain as a cron-scheduled workflow. Run history, per-run billing, and retry logic all live in the dashboard. No DevOps.
One place for every provider credential
Apollo keys, HeyReach OAuth, waterfall fallbacks (Hunter, Dropcontact, Findymail, Prospeo) — all live in the Deepline dashboard. Rotate once; every workflow picks up the new credential automatically.
What people are saying
“LinkedIn tightened enforcement in March 2025 — public company pages scraped via the old Apollo/Seamless flows started disappearing. Sales Navigator is the compliant path.”
Citations sourced from community posts, vendor case studies, and engineering blogs. See src/data/workflow-social-proof.md in the repo for the full sentiment bank.
Troubleshooting
Apollo integration shows red in the Deepline dashboard
Cause: Apollo credentials are either expired, revoked at the provider side, or the account tier doesn't expose API access.
Fix: Click the integration row in the dashboard → Test Connection. If it fails, re-paste the API key (or re-run OAuth for key-based providers). Confirm the provider account tier includes API access — most providers gate this to paid tiers.
Workflow run succeeds but 0 rows landed in the destination
Cause: The filter returned 0 matches, OR rows failed a downstream gate (email not verified, already in destination, deliverability check failed).
Fix: Open the run in the Deepline dashboard → expand the step-by-step trace. Every row's path is logged: matched/unmatched at each stage. Most frequent culprit is the email-verification gate. Loosen the filter or remove the gate in the prompt if that's the cause.
Scheduled workflow stopped firing
Cause: Either hit a provider rate-limit, ran out of Deepline credits, or the destination API returned 500s Deepline classified as permanent.
Fix: Dashboard → Workflows → Recent Runs. Failed runs show the exact error and a "Replay" button. Credits are visible top-right. Rate-limit issues auto-resume once the window resets; permanent errors need intervention.
FAQ
Do I need an Anthropic API key for this?
No. You need Claude Code (the CLI/IDE). Deepline provides the tool-execution layer and credit system. Your Claude Code subscription or Anthropic API key handles the LLM calls — Deepline handles the GTM actions underneath.
How does Deepline handle dedup across runs?
Built-in. For HeyReach as a destination, Deepline uses the provider-native idempotency key (email for HubSpot/Attio, External_Id for Salesforce, campaign-level dedup for Instantly/Smartlead/Lemlist). Reruns update existing records instead of creating duplicates.
Can I still use my own API keys?
Yes. Paste them in the Deepline dashboard under Integrations. Deepline uses your keys for the actual provider calls — you keep your provider contracts, billing, and rate limit allocation. Deepline's credit billing only covers the orchestration + waterfall layer.
What if my filter only matches 3 rows but the workflow says 1000?
Deepline runs exactly what you describe. The 1000 in cost-math is the reference cost per 1K rows — a 3-row run costs 3/1000 of that total. You never pay for rows that don't exist.
Can I combine this with a waterfall?
Yes. Mention it in the prompt — e.g. "If Apollo doesn't return an email, fall back to Hunter → Dropcontact → Findymail." Deepline assembles the waterfall automatically and charges you only for the provider that successfully finds each row.
Related workflows
Apollo → Instantly
Install Deepline, connect Apollo and Instantly in the dashboard, then tell Claude exactly who you want and which campaign to drop them into. Deploy the exact prompt as a recurring workflow and it runs every morning.
Apollo → Lemlist
Connect Apollo and Lemlist in Deepline, describe the filter, and Claude pulls + verifies + imports. Lemlist's multi-channel sequences (email + LinkedIn) pair naturally with Apollo's firmographic filters.
LinkedIn (post commenters) → Lemlist
Connect the LinkedIn scraper and Lemlist in Deepline, paste a post URL into the chat, and Claude scrapes commenters, runs the email waterfall, generates first lines, and drops everyone into your Lemlist campaign.
Want this workflow pre-configured?
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.