
Source
Influencers.club
Destination
Meta Audiences
Run Influencers.club Audience Overlap through Deepline, route the paid audience activation output, 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 docs.
Influencers.club Influencers Club Audience Overlap API to Meta Audiences is a supported Deepline workflow path. Use it when an agent needs to run Influencers.club Influencers Club Audience Overlap API, inspect the returned fields, and write the reviewed result into Meta Audiences with run history, retries, and explicit failure states.
Use when
You need Influencers.club influencers club audience overlap api reviewed before it writes into Meta Audiences.
Source output
Influencers.club influencers club audience overlap api returns structured fields that Deepline records with provider attribution and row-level status.
Destination write
Meta Audiences receives only reviewed rows after the pilot command succeeds.
This workflow moves data from Influencers.club into Meta Audiences with Deepline as the orchestration layer. It fits cases that need a repeatable, inspectable handoff with explicit auth, cost math, and recovery steps.
Quickstart setup
npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --jsonInfluencers.club Normalized provider record → Deepline normalized run output
id, url, domain, email, or provider key
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 → 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 agents a tested API surface instead of a browser-only workflow.
npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --jsonConnect Influencers.club in the Deepline dashboard. Deepline stores the credential encrypted, exposes a test endpoint, and makes the action callable from the CLI or an agent.
Connect Meta Audiences as the destination. Use the provider page to confirm required scopes before writing data. Destination reference: https://deepline.com/integrations/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 record identifier, matched entity, provider attribution plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv \
--with 'result=influencers_club_audience_overlap:{}' \
--rows 0:2 --json
# Review the pilot output, then map the result into Meta Audiences.After the pilot is correct, deploy the exact prompt as a Deepline workflow. The mapping from Influencers.club to Meta Audiences is preserved with run history, retries, billing visibility, and a rollback tag.
> Use Influencers.club Audience Overlap to enrich the input normalized provider record, 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.
Deepline exposes the Influencers.club action, runs a pilot, records the output, and writes 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 Influencers.club 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 Influencers.club 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.
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.
Run X Ads Audiences Create Audience through Deepline, route the paid audience activation output, 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 docs.
Run LeadMagic Email Finder through Deepline, route the contact discovery output, 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 docs.
Run LeadMagic Email Validation through Deepline, route the email verification output, 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 docs.
Run Snowflake Query ad audience emails through Deepline, route the paid audience activation output, 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 docs.
Run DiscoLike Cancel Contacts Run through Deepline, route the contact discovery output, 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 docs.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.