Source
LeadMagic
DeeplineWorkflow runpilot · inspect · write
Destination
LinkedIn Ads Audiences
How to Use LeadMagic Email Finder in Deepline
Run LeadMagic Email Finder through Deepline, route the contact discovery output, 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 docs.
LeadMagic Email Finder to LinkedIn Ads Audiences workflow
LeadMagic Email Finder to LinkedIn Ads Audiences is a supported Deepline workflow path. Use it when an agent needs to run LeadMagic Email Finder, inspect the returned fields, and write the reviewed result into LinkedIn Ads Audiences with run history, retries, and explicit failure states.
Use when
You need LeadMagic email finder reviewed before it writes into LinkedIn Ads Audiences.
Source output
LeadMagic email finder returns structured fields that Deepline records with provider attribution and row-level status.
Destination write
LinkedIn Ads Audiences receives only reviewed rows after the pilot command succeeds.
This workflow moves data from LeadMagic into LinkedIn Ads Audiences with Deepline as the orchestration layer. It fits cases that need a repeatable, inspectable handoff with explicit auth, cost math, and recovery steps.
- Source app
- LeadMagic
- Destination app
- LinkedIn Ads Audiences
- Run time
- 3 min
- Difficulty
- beginner
- Agent surface
- Deepline CLI, API, and workflow scheduler
- Write policy
- Two-row pilot before destination writes
- LeadMagic auth
- Handled by Deepline -- connect once in the dashboard
- LinkedIn Ads Audiences auth
- Handled by Deepline -- connect once in the dashboard
- LeadMagic tier
- Any plan with the required API access
- LinkedIn Ads Audiences tier
- LinkedIn Ads account with audience permissions
Quickstart setup
npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --jsonFields agents can extract and verify
LeadMagic source data points
- Email result
- email, status, confidence, catch_all
- Job-change signal
- old_company, new_company, title, detected_at
- Company match
- company_name, domain, linkedin_url
- Ads and search context
- keyword, advertiser, ad_url, landing_page
LinkedIn Ads Audiences destination mapping
LeadMagic 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.
- LeadMagic account (Any plan with the required API access)
- LinkedIn Ads Audiences account (LinkedIn Ads account with audience permissions)
- Deepline CLI installed locally
- ~3 minutes
Step-by-step
- 01
Install Deepline
Install the Deepline CLI and register your workspace. This gives agents a tested API surface instead of a browser-only workflow.
npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --json - 02
Connect LeadMagic
Connect LeadMagic in the Deepline dashboard. Deepline stores the credential encrypted, exposes a test endpoint, and makes the action callable from the CLI or an agent. Provider reference: https://deepline.com/integrations/leadmagic.
- 03
Connect LinkedIn Ads Audiences
Connect LinkedIn Ads Audiences as the destination. Use the provider page to confirm required scopes before writing data. Destination reference: https://deepline.com/integrations/linkedin_ads_audiences.
- 04
Run a two-row pilot
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"}' --json - 05
Deploy the reviewed prompt
After the pilot is correct, 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.
What this costs to run
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.
Why run it through Deepline
The workflow stays inspectable
Deepline exposes the LeadMagic action, runs a pilot, records the output, and writes only reviewed rows to LinkedIn Ads Audiences.
Provider docs and GTM Stack pages are linked
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.
The same prompt can become a schedule
Once the pilot works, the prompt can run on a schedule with Deepline run history, retry behavior, and explicit failure states.
Troubleshooting
LeadMagic returns no rows
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.
LinkedIn Ads Audiences rejects the write
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.
The workflow works once but fails on a schedule
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.
FAQ
Can Deepline run LeadMagic Email Finder directly?
Yes. Deepline exposes the LeadMagic action as an agent-callable API and CLI step, so you can run a pilot, inspect the JSON, and then deploy the same logic as a workflow.
Should I write directly to LinkedIn Ads Audiences?
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.
How does this page help agents trust the workflow?
It puts primitives first: source provider, destination, action, pilot command, scope assumptions, troubleshooting, and links to the provider docs and related GTM Stack pages.
Keep exploring
LeadMagic → HubSpot
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.
LeadMagic → Instantly
Connect LeadMagic and Instantly in Deepline, give Claude a name+company list, and it resolves emails + imports into Instantly.
LeadMagic → Smartlead
Connect LeadMagic and Smartlead in Deepline, describe the ICP, and Claude enriches + imports.
LeadMagic → Salesforce
Connect LeadMagic and Salesforce in Deepline, pass the list, and Claude resolves + upserts Salesforce Leads.
LeadMagic → Attio
Connect LeadMagic and Attio in Deepline, pass the list, and Claude resolves + upserts. Idempotent by email.
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.