Run Hunter Email Finder from Claude Code, route the contact discovery output through Deepline, and write the reviewed result into Meta Audiences. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
Hunter to Meta Audiences is a supported Deepline workflow path for Claude Code. Use it when an agent needs to run Hunter, inspect the returned fields, and write the reviewed result into Meta Audiences with run history, retries, and explicit failure states.
Best query match
“How do I connect Hunter to Meta Audiences with Claude Code?”
Source primitive
Hunter returns structured fields that Deepline records with provider attribution and row-level status.
Destination primitive
Meta Audiences receives only reviewed rows after the pilot command succeeds.
This workflow moves data from Hunter into Meta 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 registerHunter Email result → Deepline normalized run output
email, domain, confidence, verification_status, first_name, last_name
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 → Meta Audiences Custom audience member
hashed_identifier, audience_id, segment, source_run_id, run ID, hashed email or phone, audience ID
Send only consented identifiers and keep non-ad fields inside Deepline or the CRM.
Meta audience size and match review → 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 Hunter 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/hunter.
Connect Meta Audiences as the destination. Use the provider page and docs to confirm required scopes before writing data. Destination reference: https://deepline.com/docs/providers/meta-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 address, person context, domain pattern plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=hunter_email_finder:{"domain":"{{domain}}","first_name":"{{first_name}}","last_name":"{{last_name}}"}' --jsonAfter the pilot is correct, ask Claude Code to deploy the exact prompt as a Deepline workflow. The mapping from Hunter to Meta Audiences is preserved with run history, retries, billing visibility, and a rollback tag.
> Use Hunter Email Finder to enrich the input email result, dedupe by domain and email, write results into Meta 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 Hunter action, run a pilot, inspect the output, and then write only reviewed rows to Meta 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 Hunter 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 Meta 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 Hunter 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 Hunter and Instantly in Deepline, describe the domain list or name+company targets, and Claude runs the email finder + verifier + Instantly import. Hunter's verifier drops invalid addresses before they hit Instantly.
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.
Connect Hunter and HubSpot in Deepline, pass a domain list and target role, and Claude runs Hunter's domain-search + verifier + HubSpot upsert.
Connect Hunter and Salesforce in Deepline, pass a domain list and target role, and Claude runs domain-search + verifier + Salesforce upsert.
Connect Hunter and Attio in Deepline, pass a domain list + role, and Claude runs Hunter + Attio upsert. 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.