Run Apollo Reveal Person from Claude Code, route the contact discovery output through Deepline, and write the reviewed result into Google Ads Audiences. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
Apollo to Google Ads Audiences is a supported Deepline workflow path for Claude Code. Use it when an agent needs to run Apollo, inspect the returned fields, and write the reviewed result into Google Ads Audiences with run history, retries, and explicit failure states.
Best query match
“How do I connect Apollo to Google Ads Audiences with Claude Code?”
Source primitive
Apollo returns structured fields that Deepline records with provider attribution and row-level status.
Destination primitive
Google Ads Audiences receives only reviewed rows after the pilot command succeeds.
This workflow moves data from Apollo into Google Ads 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 registerApollo Person → Deepline normalized run output
email, linkedin_url, first_name, last_name, title, seniority
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 → Google Ads Audiences Customer Match member
hashed_identifier, audience_id, segment_name, source_run_id, run ID, hashed identifier, audience ID
Use this destination for activation segments, not raw research notes.
Google Ads audience 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 Apollo 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/apollo.
Connect Google Ads Audiences as the destination. Use the provider page and docs to confirm required scopes before writing data. Destination reference: https://deepline.com/docs/providers/google-ads-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 person identity, company context, email candidate plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv \
--with 'result=apollo_reveal_person:{}' \
--rows 0:2 --json
# Review the pilot output, then map the result into Google Ads Audiences.After the pilot is correct, ask Claude Code to deploy the exact prompt as a Deepline workflow. The mapping from Apollo to Google Ads Audiences is preserved with run history, retries, billing visibility, and a rollback tag.
> Use Apollo Reveal Person to enrich the input person, dedupe by domain and email, write results into Google Ads 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 Apollo action, run a pilot, inspect the output, and then write only reviewed rows to Google Ads 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 Apollo 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 Google Ads 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 Apollo 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.
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 the LinkedIn scraper and Lemlist in Deepline, paste a post URL into the chat, and Claude scrapes commenters, runs the email waterfall, generates first lines, and drops everyone into your Lemlist campaign.
Connect Apollo and Salesforce in Deepline, define your filter in the chat, and Claude runs the search + enrich + upsert. Deepline uses Apollo's person_id as External ID so reruns update existing Leads, never duplicate.
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.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.