Connect the LinkedIn scraper + HeyReach in Deepline, paste a post URL, and Claude scrapes commenters + pushes directly to HeyReach (LinkedIn URLs, no email needed).
LinkedIn (post commenters, via Apify) to HeyReach is a supported Deepline workflow path for Claude Code. Use it when an agent needs to run LinkedIn (post commenters, via Apify), inspect the returned fields, and write the reviewed result into HeyReach with run history, retries, and explicit failure states.
Best query match
“How do I connect LinkedIn (post commenters, via Apify) to HeyReach with Claude Code?”
Source primitive
LinkedIn (post commenters, via Apify) returns structured fields that Deepline records with provider attribution and row-level status.
Destination primitive
HeyReach receives only reviewed rows after the pilot command succeeds.
This workflow moves data from LinkedIn (post commenters, via Apify) into HeyReach with Claude Code as the orchestration layer. It is strongest when you need a repeatable, inspectable handoff with explicit auth, cost math, and recovery steps.
First callable command
curl -s "https://code.deepline.com/api/v2/cli/install" | bash
deepline auth registerOne 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 registerConnect via Apify or ContactOut in the Deepline dashboard — LinkedIn Sales Navigator itself has no public API. Deepline uses an Apify actor for scraped data or ContactOut for verified profiles, both paste-your-key flows.
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.
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:
> Scrape commenters on this LinkedIn post. Normalize LinkedIn URLs. Add to HeyReach campaign 'Post Engagement LinkedIn Outreach' with the original comment text and source_post_url as custom fields. Skip the email waterfall entirely — LinkedIn URLs are enough for HeyReach.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.For 1,000 leads: $0.50
~0.05 credits per commenter added. No email waterfall cost. Deepline's credit pricing is pay-as-you-go — see code.deepline.com/docs/pricing for current rates.
Deepline tries the cheapest provider first and only falls back if it misses. For LinkedIn (post commenters, via Apify) 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.
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.
LinkedIn (post commenters, via Apify) 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.
“LinkedIn post commenters are one of the highest-intent audiences available — they self-selected by reacting to exactly the problem your product solves.”
Citations sourced from community posts, vendor case studies, and engineering blogs.
Cause: LinkedIn (post commenters, via Apify) 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.
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.
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.
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.
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.
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.
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.
Yes. Mention it in the prompt — e.g. "If LinkedIn (post commenters, via Apify) 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.
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.
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.
Connect Apify + HeyReach in Deepline, give Claude a Sales Nav URL, and it scrapes + pushes to HeyReach. No email resolution — LinkedIn URLs are enough.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.