Source
Reo.dev
DeeplineWorkflow runpilot · inspect · write
Destination
LinkedIn Ads Audiences
How to Use Reo.dev Get Audience Members in Deepline
Run Reo.dev Get Audience Members through Deepline, route the paid audience activation output, and write the reviewed result into LinkedIn Ads Audiences. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
Reo.dev Reo Get Audience Members API to LinkedIn Ads Audiences workflow
Reo.dev Reo Get Audience Members API to LinkedIn Ads Audiences is a supported Deepline workflow path. Use it when an agent needs to run Reo.dev Reo Get Audience Members API, inspect the returned fields, and write the reviewed result into LinkedIn Ads Audiences with run history, retries, and explicit failure states.
Use when
You need Reo.dev reo get audience members api reviewed before it writes into LinkedIn Ads Audiences.
Source output
Reo.dev reo get audience members api returns structured fields that Deepline records with provider attribution and row-level status.
Destination write
LinkedIn Ads Audiences receives only reviewed rows after the pilot command succeeds.
This workflow moves data from Reo.dev into LinkedIn Ads Audiences 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
- Reo.dev
- Destination app
- LinkedIn Ads Audiences
- Run time
- 3 min
- Difficulty
- beginner
- Agent surface
- Deepline CLI, API, and workflow scheduler
- Write policy
- Two-row pilot before destination writes
- Reo.dev auth
- Handled by Deepline -- connect once in the dashboard
- LinkedIn Ads Audiences auth
- Handled by Deepline -- connect once in the dashboard
- Reo.dev tier
- Any plan with the required API access
- LinkedIn Ads Audiences tier
- LinkedIn Ads account with audience permissions
Quickstart setup
npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --jsonFields agents can extract and verify
Reo.dev source data points
- Record identifier
- id, url, domain, email, or provider key
- Matched entity
- person, company, account, page, query, or signal
- Provider attribution
- provider, action, run_id, retrieved_at
- Review status
- accepted, rejected, needs_review
LinkedIn Ads Audiences destination mapping
Reo.dev 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 → LinkedIn Ads Audiences Review row
source_key, summary, mapped_fields, review_status, run ID, record key, normalized provider fields
Map the smallest useful field set first, then expand the destination schema once the two-row pilot is correct.
LinkedIn Ads Audiences review view → 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.
- Reo.dev account (Any plan with the required API access)
- LinkedIn Ads Audiences account (LinkedIn Ads account with audience permissions)
- Deepline CLI installed locally
- ~3 minutes
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 Reo.dev
Connect Reo.dev 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/reo.
- 03
Connect LinkedIn Ads Audiences
Connect LinkedIn Ads Audiences as the destination. Use the provider page to confirm required scopes before writing data. Destination reference: https://deepline.com/integrations/linkedin_ads_audiences.
- 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 record identifier, matched entity, provider attribution plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv \ --with 'result=reo_get_audience_members:{}' \ --rows 0:2 --json # Review the pilot output, then map the result into LinkedIn Ads Audiences. - 05
Deploy the reviewed prompt
After the pilot is correct, deploy the exact prompt as a Deepline workflow. The mapping from Reo.dev to LinkedIn Ads Audiences is preserved with run history, retries, billing visibility, and a rollback tag.
> Use Reo.dev Get Audience Members to enrich the input normalized provider record, dedupe by domain and email, write results into LinkedIn Ads Audiences, and show me the exact rows that changed before deploying the workflow.
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 Reo.dev action, runs a pilot, records the output, and writes only reviewed rows to LinkedIn Ads Audiences.
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
Reo.dev 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 Reo.dev integration in Deepline, run the test endpoint, and then retry the workflow on --rows 0:2 with a broader filter.
LinkedIn Ads Audiences rejects the write
Cause: The destination field names, object IDs, campaign IDs, or permissions do not match the connected workspace.
Fix: Use the LinkedIn Ads Audiences 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 Reo.dev Get Audience Members directly?
Yes. Deepline exposes the Reo.dev 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 LinkedIn Ads Audiences?
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
LeadMagic → LinkedIn Ads Audiences
Run LeadMagic Email Finder through Deepline, route the contact discovery output, and write the reviewed result into LinkedIn Ads Audiences. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
Snowflake → LinkedIn Ads Audiences
Run Snowflake Query ad audience emails through Deepline, route the paid audience activation output, and write the reviewed result into LinkedIn Ads Audiences. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
LeadMagic → LinkedIn Ads Audiences
Run LeadMagic Email Validation through Deepline, route the email verification output, and write the reviewed result into LinkedIn Ads Audiences. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
LeadMagic → LinkedIn Ads Audiences
Run LeadMagic Role Finder through Deepline, route the contact discovery output, and write the reviewed result into LinkedIn Ads Audiences. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
LeadMagic → LinkedIn Ads Audiences
Run LeadMagic B2b Social Email through Deepline, route the contact discovery output, and write the reviewed result into LinkedIn Ads Audiences. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
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.