Source
LeadMagic
DeeplineWorkflow runpilot · inspect · write
Destination
Instantly
How to Use LeadMagic Email Validation in Deepline
Run LeadMagic Email Validation through Deepline, route the email verification output, and write the reviewed result into Instantly. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
LeadMagic Email Validation to Instantly workflow
LeadMagic Email Validation to Instantly is a supported Deepline workflow path. Use it when an agent needs to run LeadMagic Email Validation, inspect the returned fields, and write the reviewed result into Instantly with run history, retries, and explicit failure states.
Use when
You need LeadMagic email validation reviewed before it writes into Instantly.
Source output
LeadMagic email validation returns structured fields that Deepline records with provider attribution and row-level status.
Destination write
Instantly receives only reviewed rows after the pilot command succeeds.
This workflow moves data from LeadMagic into Instantly 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
- Instantly
- 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
- Instantly auth
- Handled by Deepline -- connect once in the dashboard
- LeadMagic tier
- Any plan with the required API access
- Instantly tier
- Any plan with API access
Quickstart setup
curl -fsSL "https://deepline.com/api/v2/sdk/install" | bashFields 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
Instantly 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 → Instantly Campaign lead
email, name, company, campaign_id, run ID, first_name, last_name
Only push contacts that pass dedupe and deliverability gates; keep source context as custom variables.
Instantly campaign lead list → 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.
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.
curl -fsSL "https://deepline.com/api/v2/sdk/install" | bash - 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 Instantly
Connect Instantly as the destination. Use the provider page to confirm required scopes before writing data. Destination reference: https://deepline.com/integrations/instantly.
- 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_validation:{"email":"{{email}}"}' --json - 05
Deploy the reviewed prompt
After the pilot is correct, deploy the exact prompt as a Deepline workflow. The mapping from LeadMagic to Instantly is preserved with run history, retries, billing visibility, and a rollback tag.
> Run LeadMagic Email Validation on the input list, keep only usable email result, write provider attribution and status into Instantly, and block campaign pushes until the pilot rows pass review.
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 Instantly.
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.
Instantly rejects the write
Cause: The destination field names, object IDs, campaign IDs, or permissions do not match the connected workspace.
Fix: Use the Instantly 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 Validation 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 Instantly?
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
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.
Clay (via webhook) → Instantly
Point your Clay table's HTTP API action at the Deepline webhook URL. Chat with Claude to define what happens on each row — verify email, enrich, drop into Instantly. Deepline handles the rest with waterfall pricing instead of per-row Clay credits.
ZoomInfo → Instantly
Connect ZoomInfo and Instantly in Deepline, describe your ICP contacts in the chat, and Claude pulls + enriches + pushes to the Instantly campaign. Deepline handles ZoomInfo's JWT rotation automatically.
Instantly (webhooks) → HubSpot
Configure Instantly to send webhooks to Deepline, then tell Claude how each event should update the matching HubSpot Contact. Deepline verifies HMAC signatures and handles the Contact lookup automatically.
Crunchbase → Instantly
Connect Crunchbase and Instantly in Deepline, tell Claude the funding thresholds and target titles, and it finds the decision makers + pushes to a dedicated campaign. Deploy weekly to catch every fresh round.
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.