Source
MillionVerifier
DeeplineWorkflow runpilot · inspect · write
Destination
HeyReach
How to Use MillionVerifier Verify Email in Deepline
Run MillionVerifier Verify Email through Deepline, route the email verification output, and write the reviewed result into HeyReach. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
MillionVerifier Verify Email API to HeyReach workflow
MillionVerifier Verify Email API to HeyReach is a supported Deepline workflow path. Use it when an agent needs to run MillionVerifier Verify Email API, inspect the returned fields, and write the reviewed result into HeyReach with run history, retries, and explicit failure states.
Use when
You need MillionVerifier verify email api reviewed before it writes into HeyReach.
Source output
MillionVerifier verify email api returns structured fields that Deepline records with provider attribution and row-level status.
Destination write
HeyReach receives only reviewed rows after the pilot command succeeds.
This workflow moves data from MillionVerifier into HeyReach 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
- MillionVerifier
- Destination app
- HeyReach
- Run time
- 3 min
- Difficulty
- beginner
- Agent surface
- Deepline CLI, API, and workflow scheduler
- Write policy
- Two-row pilot before destination writes
- MillionVerifier auth
- Handled by Deepline -- connect once in the dashboard
- HeyReach auth
- Handled by Deepline -- connect once in the dashboard
- MillionVerifier tier
- MillionVerifier account with API access
- HeyReach tier
- Any plan with API access
Quickstart setup
npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --jsonFields agents can extract and verify
MillionVerifier source data points
- Verification result
- result, quality, sub_status
- Email components
- email, domain, mx_records
- Risk categories
- disposable, free, role, catch_all
- Provider attribution
- provider, checked_at, run_id
HeyReach destination mapping
MillionVerifier Normalized provider record → Deepline normalized run output
id, url, result, quality, sub_status, email, domain
Claude Code sees the normalized provider record as structured JSON, then Deepline adds provider name, action slug, run ID, retrieved timestamp, and row-level status.
Deepline normalized run output → HeyReach Campaign lead
email, name, company, campaign_id, run ID, linkedin_url, message variables
Use HeyReach only after the workflow verifies LinkedIn URLs and message context.
HeyReach campaign queue → 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.
- MillionVerifier account (MillionVerifier account with API access)
- HeyReach account (Any plan with API access)
- 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 MillionVerifier
Connect MillionVerifier 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/millionverifier.
- 03
Connect HeyReach
Connect HeyReach as the destination. Use the provider page to confirm required scopes before writing data. Destination reference: https://deepline.com/integrations/heyreach.
- 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 verification result, email components, risk categories plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv \ --with 'result=millionverifier_verify_email:{}' \ --rows 0:2 --json # Review the pilot output, then map the result into HeyReach. - 05
Deploy the reviewed prompt
After the pilot is correct, deploy the exact prompt as a Deepline workflow. The mapping from MillionVerifier to HeyReach is preserved with run history, retries, billing visibility, and a rollback tag.
> Run MillionVerifier Verify Email on the input list, keep only usable normalized provider record, write provider attribution and status into HeyReach, 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 MillionVerifier action, runs a pilot, records the output, and writes only reviewed rows to HeyReach.
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
MillionVerifier 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 MillionVerifier integration in Deepline, run the test endpoint, and then retry the workflow on --rows 0:2 with a broader filter.
HeyReach rejects the write
Cause: The destination field names, object IDs, campaign IDs, or permissions do not match the connected workspace.
Fix: Use the HeyReach 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 MillionVerifier Verify Email directly?
Yes. Deepline exposes the MillionVerifier 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 HeyReach?
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 → HeyReach
Connect Apollo and HeyReach in Deepline, describe the ICP, and Claude filters for LinkedIn URLs + normalizes them + pushes to the HeyReach campaign. Respects LinkedIn's 50-100 invites/day cap automatically.
HubSpot → HeyReach
Connect HubSpot and HeyReach in Deepline, describe the segment, and Claude filters for LinkedIn URL presence + pushes to HeyReach with hubspot_contact_id tagged.
Salesforce → HeyReach
Connect Salesforce and HeyReach in Deepline, define the SOQL filter, and Claude runs the pull + URL normalization + HeyReach import.
ZoomInfo → HeyReach
Connect ZoomInfo and HeyReach in Deepline, describe the persona + firmographics, and Claude pulls ZoomInfo + filters to LinkedIn-URL presence + pushes to HeyReach. Respects LinkedIn's daily invite cap per account.
People Data Labs → HeyReach
Connect PDL and HeyReach in Deepline, describe the ICP, and Claude runs ES-DSL search + LinkedIn-URL filter + HeyReach import.
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.