Run ZeroBounce Activity Data from Claude Code, route the email verification output through Deepline, and write the reviewed result into Smartlead. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
ZeroBounce to Smartlead is a supported Deepline workflow path for Claude Code. Use it when an agent needs to run ZeroBounce, inspect the returned fields, and write the reviewed result into Smartlead with run history, retries, and explicit failure states.
Best query match
“How do I connect ZeroBounce to Smartlead with Claude Code?”
Source primitive
ZeroBounce returns structured fields that Deepline records with provider attribution and row-level status.
Destination primitive
Smartlead receives only reviewed rows after the pilot command succeeds.
This workflow moves data from ZeroBounce into Smartlead 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 registerZeroBounce Email address → Deepline normalized run output
email, batch_id, valid, invalid, catch_all, do_not_mail, spamtrap
Claude Code sees the email address as structured JSON, then Deepline adds provider name, action slug, run ID, retrieved timestamp, and row-level status.
Deepline normalized run output → Smartlead Campaign lead
email, name, company, campaign_id, run ID, custom fields
Custom fields should carry the exact trigger, source URL, or keyword that caused the contact to enter the campaign.
Smartlead 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.
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 ZeroBounce 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/zerobounce.
Connect Smartlead as the destination. Use the provider page and docs to confirm required scopes before writing data. Destination reference: https://deepline.com/docs/providers/smartlead.
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 status, risk detail, email metadata plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=zerobounce_activity_data:{"email":"{{email}}"}' --jsonAfter the pilot is correct, ask Claude Code to deploy the exact prompt as a Deepline workflow. The mapping from ZeroBounce to Smartlead is preserved with run history, retries, billing visibility, and a rollback tag.
> Run ZeroBounce Activity Data on the input list, keep only usable email address, write provider attribution and status into Smartlead, and block campaign pushes until the pilot rows pass review.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 ZeroBounce action, run a pilot, inspect the output, and then write only reviewed rows to Smartlead.
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 ZeroBounce 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 Smartlead 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 ZeroBounce 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 Apollo and Smartlead in the Deepline dashboard, tell Claude the filter and target campaign, and deploy the prompt as a recurring workflow. Deepline handles email verification and campaign dedup automatically.
Connect ZoomInfo and Smartlead in Deepline, describe the persona + industry + region, and Claude does the rest. Deepline batches 100 per Smartlead import call without you thinking about it.
Connect HubSpot and Smartlead in Deepline, describe the segment (lifecycle stage, last contacted, list membership), and Claude runs the export + Smartlead import. Includes hubspot_contact_id in custom fields for the return-trip feedback loop.
Point Smartlead webhooks at Deepline, describe the routing rules in the chat, and every campaign event updates the matching HubSpot Contact. HMAC verification + lookup handled for you.
Connect Hunter and Smartlead in Deepline, pass the domain list + target roles, and Claude runs email-finder + verifier + Smartlead import. Verified-only lands in Smartlead.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.