Run FindyMail Enrich Company from Claude Code, route the signal-based selling output through Deepline, 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-doc links.
FindyMail to Instantly is a supported Deepline workflow path for Claude Code. Use it when an agent needs to run FindyMail, inspect the returned fields, and write the reviewed result into Instantly with run history, retries, and explicit failure states.
Best query match
“How do I connect FindyMail to Instantly with Claude Code?”
Source primitive
FindyMail returns structured fields that Deepline records with provider attribution and row-level status.
Destination primitive
Instantly receives only reviewed rows after the pilot command succeeds.
This workflow moves data from FindyMail into Instantly 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 registerFindyMail 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 → 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.
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 FindyMail 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/findymail.
Connect Instantly as the destination. Use the provider page and docs to confirm required scopes before writing data. Destination reference: https://deepline.com/docs/providers/instantly.
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 candidate, input identity, deliverability context plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=findymail_enrich_company:{}' --jsonAfter the pilot is correct, ask Claude Code to deploy the exact prompt as a Deepline workflow. The mapping from FindyMail to Instantly is preserved with run history, retries, billing visibility, and a rollback tag.
> Use FindyMail Enrich Company to find new buying signals for our target accounts, score each signal by urgency and fit, write the best person into Instantly, and post anything needing human review before activation.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 FindyMail action, run a pilot, inspect the output, and then write only reviewed rows to Instantly.
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 FindyMail 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 Instantly 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 FindyMail 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.
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.
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.
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.
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.
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.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.