Source
Hunter
DeeplineWorkflow runpilot · inspect · write
Destination
HubSpot
How to Use Hunter Combined Find in Deepline
Run Hunter Combined Find through Deepline, route the signal-based selling output, and write the reviewed result into HubSpot. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
Hunter Combined Find to HubSpot workflow
Hunter Combined Find to HubSpot is a supported Deepline workflow path. Use it when an agent needs to run Hunter Combined Find, inspect the returned fields, and write the reviewed result into HubSpot with run history, retries, and explicit failure states.
Use when
You need Hunter combined find reviewed before it writes into HubSpot.
Source output
Hunter combined find returns structured fields that Deepline records with provider attribution and row-level status.
Destination write
HubSpot receives only reviewed rows after the pilot command succeeds.
This workflow moves data from Hunter into HubSpot 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
- Hunter
- Destination app
- HubSpot
- Run time
- 3 min
- Difficulty
- intermediate
- Agent surface
- Deepline CLI, API, and workflow scheduler
- Write policy
- Two-row pilot before destination writes
- Hunter auth
- Handled by Deepline -- connect once in the dashboard
- HubSpot auth
- Handled by Deepline -- connect once in the dashboard
- Hunter tier
- Any plan with the required API access
- HubSpot tier
- Any HubSpot plan with the needed CRM scopes
Quickstart setup
npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --jsonFields agents can extract and verify
Hunter source data points
- Email address
- email, confidence, verification_status
- Person context
- first_name, last_name, position, department, seniority
- Domain pattern
- domain, pattern, organization
- Public sources
- source_url, source_domain, extracted_on
HubSpot destination mapping
Hunter Person → Deepline normalized run output
email, linkedin_url, confidence, verification_status, first_name, last_name
Claude Code sees the person as structured JSON, then Deepline adds provider name, action slug, run ID, retrieved timestamp, and row-level status.
Deepline normalized run output → HubSpot CRM contact
email, name, title, company, run ID, email/domain key, source fields
Write only reviewed fields and keep provider output in a source-attribution property or timeline note.
HubSpot list, note, or task 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.
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 Hunter
Connect Hunter 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/hunter.
- 03
Connect HubSpot
Connect HubSpot as the destination. Use the provider page to confirm required scopes before writing data. Destination reference: https://deepline.com/integrations/hubspot.
- 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 address, person context, domain pattern plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=hunter_combined_find:{}' --json - 05
Deploy the reviewed prompt
After the pilot is correct, deploy the exact prompt as a Deepline workflow. The mapping from Hunter to HubSpot is preserved with run history, retries, billing visibility, and a rollback tag.
> Use Hunter Combined Find to find new buying signals for our target accounts, score each signal by urgency and fit, write the best person into HubSpot, and post anything needing human review before activation.
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 Hunter action, runs a pilot, records the output, and writes only reviewed rows to HubSpot.
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
Hunter 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 Hunter integration in Deepline, run the test endpoint, and then retry the workflow on --rows 0:2 with a broader filter.
HubSpot rejects the write
Cause: The destination field names, object IDs, campaign IDs, or permissions do not match the connected workspace.
Fix: Use the HubSpot 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 Hunter Combined Find directly?
Yes. Deepline exposes the Hunter 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 HubSpot?
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
HubSpot (field-change webhook) → Deepline Workflow (webhook-triggered)
Subscribe Deepline to HubSpot's property-change webhook, then chat with Claude to define what happens when a field flips. Works as a drop-in upgrade for Clay webhook setups — same trigger, cheaper enrichment under the hood.
ZoomInfo → HubSpot
Connect ZoomInfo and HubSpot in Deepline, describe the accounts you want in plain English, and Claude pulls + enriches + upserts. Dedupes by domain so nightly runs never create duplicates.
Clay (via webhook) → HubSpot
Point Clay's HTTP API column at the Deepline webhook, tell Claude how to shape the HubSpot Contact, and Deepline handles the batched upsert. Works as a webhook receiver for any tool that POSTs JSON.
Apollo → HubSpot
Connect Apollo and HubSpot in Deepline, tell Claude exactly who to find and how to tag them in HubSpot, and the workflow runs. Deepline batches 100 Contacts per HubSpot call and handles the 150 req/10s rate limit.
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.
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.