Connect Apify + Instantly in Deepline, give Claude a Sales Nav URL, and it scrapes + resolves emails + drops into Instantly with persona vars ready for your templates.
LinkedIn Sales Navigator (via Apify) to Instantly is a supported Deepline workflow path for Claude Code. Use it when an agent needs to run LinkedIn Sales Navigator (via Apify), inspect the returned fields, and write the reviewed result into Instantly with run history, retries, and explicit failure states.
Best query match
“How do I connect LinkedIn Sales Navigator (via Apify) to Instantly with Claude Code?”
Source primitive
LinkedIn Sales Navigator (via Apify) returns structured fields that Deepline records with provider attribution and row-level status.
Destination primitive
Instantly receives only reviewed rows after the pilot command succeeds.
This workflow moves data from LinkedIn Sales Navigator (via Apify) into Instantly 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 → Instantly → paste your API key from Instantly Settings → Integrations. Deepline will auto-list your active campaigns so you can pick the destination per run.
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 the 500 profiles in this Sales Nav saved search. Resolve work emails via waterfall. Push verified emails into Instantly campaign "Sales Nav Outbound" with linkedin_url, current_company, and current_title as custom variables.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: $3.00
~0.3 credits per verified email pushed to Instantly. Waterfall cost dominates; typical 60-75% hit rate. 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 Sales Navigator (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 Sales Navigator (via Apify) keys, Instantly 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 Sales Navigator (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 Instantly 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 Sales Navigator (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.
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.
Connect Apify + HubSpot in Deepline, give Claude a Sales Nav search URL, and it scrapes profiles + runs email waterfall + upserts HubSpot Contacts with persona attributes intact.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.