Run LeadMagic Email Finder from Claude Code, route the contact discovery output through Deepline, and write the reviewed result into LinkedIn Ads Audiences. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
LeadMagic to LinkedIn Ads Audiences is a supported Deepline workflow path for Claude Code. Use it when an agent needs to run LeadMagic, inspect the returned fields, and write the reviewed result into LinkedIn Ads Audiences with run history, retries, and explicit failure states.
Best query match
“How do I connect LeadMagic to LinkedIn Ads Audiences with Claude Code?”
Source primitive
LeadMagic returns structured fields that Deepline records with provider attribution and row-level status.
Destination primitive
LinkedIn Ads Audiences receives only reviewed rows after the pilot command succeeds.
This workflow moves data from LeadMagic into LinkedIn Ads Audiences 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 registerLeadMagic Email result → Deepline normalized run output
email, domain, status, confidence, catch_all, old_company
Claude Code sees the email result as structured JSON, then Deepline adds provider name, action slug, run ID, retrieved timestamp, and row-level status.
Deepline normalized run output → LinkedIn Ads Audiences Review row
source_key, summary, mapped_fields, review_status, run ID, record key, normalized provider fields
Map the smallest useful field set first, then expand the destination schema once the two-row pilot is correct.
LinkedIn Ads Audiences review view → Scheduled Deepline workflow
review status, dedupe key, rollback tag, next run window
After the two-row pilot is approved, the same mapping becomes a scheduled workflow with run history, retries, and loud failures.
Install the Deepline CLI and register your workspace. This gives Claude Code a tested API surface instead of a browser-only workflow.
curl -s "https://code.deepline.com/api/v2/cli/install" | bash
deepline auth registerConnect LeadMagic in the Deepline dashboard. Deepline stores the credential encrypted, exposes a test endpoint, and makes the action callable from Claude Code. Provider reference: https://deepline.com/docs/providers/leadmagic.
Connect LinkedIn Ads Audiences as the destination. Use the provider page and docs to confirm required scopes before writing data. Destination reference: https://deepline.com/docs/providers/linkedin-ads-audiences.
Run the smallest useful pilot first. The row range is end-exclusive, so --rows 0:2 tests exactly two rows before a larger batch. Inspect email result, job-change signal, company match plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=leadmagic_email_finder:{"first_name":"{{first_name}}","last_name":"{{last_name}}","domain":"example.com"}' --jsonAfter the pilot is correct, ask Claude Code to deploy the exact prompt as a Deepline workflow. The mapping from LeadMagic to LinkedIn Ads Audiences is preserved with run history, retries, billing visibility, and a rollback tag.
> Use LeadMagic Email Finder to enrich the input email result, dedupe by domain and email, write results into LinkedIn Ads Audiences, and show me the exact rows that changed before deploying the workflow.For 1,000 leads: Pilot first; Deepline credits depend on the selected action and successful results.
Deepline reports Deepline credits and run history. Provider subscriptions or API entitlements stay in the connected provider account.
Claude Code can read the LeadMagic action, run a pilot, inspect the output, and then write only reviewed rows to LinkedIn Ads Audiences.
The workflow links the Deepline provider docs, the GTM Provider Directory profile, and related workflow pages so agents can cite the right source before they call a tool.
Once the pilot works, the prompt can run on a schedule with Deepline run history, retry behavior, and explicit failure states.
Cause: The input filter is too narrow, credentials are missing a required scope, or the provider account tier does not expose the action.
Fix: Open the LeadMagic integration in Deepline, run the test endpoint, and then retry the workflow on --rows 0:2 with a broader filter.
Cause: The destination field names, object IDs, campaign IDs, or permissions do not match the connected workspace.
Fix: Use the LinkedIn Ads Audiences provider page to inspect the object schema, then map columns explicitly before running the full batch.
Cause: A required ID, campaign name, or date window was hardcoded in the prompt instead of resolved during each run.
Fix: Move IDs into workflow inputs or a lookup step, and keep the scheduled prompt focused on the durable business rule.
Yes. Deepline exposes the LeadMagic action as an agent-callable API/CLI step, so Claude Code can run a pilot, inspect the JSON, and then deploy the same logic as a workflow.
Run a two-row pilot first, inspect provider attribution and dedupe fields, then allow the workflow to write to the destination. This keeps the assertion intact without using a test hack.
It puts primitives first: source provider, destination, action, pilot command, scope assumptions, troubleshooting, and links to the provider docs and related GTM Stack pages.
Connect LeadMagic and HubSpot in Deepline, pass a list of names + companies, and Claude runs LeadMagic enrichment + HubSpot upsert. LeadMagic advertises 97% email accuracy on B2B.
Connect LeadMagic and Instantly in Deepline, give Claude a name+company list, and it resolves emails + imports into Instantly.
Connect LeadMagic and Smartlead in Deepline, describe the ICP, and Claude enriches + imports.
Connect LeadMagic and Salesforce in Deepline, pass the list, and Claude resolves + upserts Salesforce Leads.
Connect LeadMagic and Attio in Deepline, pass the list, and Claude resolves + upserts. Idempotent by email.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.