Connect PDL and Salesforce in Deepline, describe the ICP as an ES-DSL query, and Claude runs search + enrich + Salesforce upsert using pdl_id as External_Id__c. Idempotent across reruns.
People Data Labs to Salesforce is a supported Deepline workflow path for Claude Code. Use it when an agent needs to run People Data Labs, inspect the returned fields, and write the reviewed result into Salesforce with run history, retries, and explicit failure states.
Best query match
“How do I connect People Data Labs to Salesforce with Claude Code?”
Source primitive
People Data Labs returns structured fields that Deepline records with provider attribution and row-level status.
Destination primitive
Salesforce receives only reviewed rows after the pilot command succeeds.
This workflow moves data from People Data Labs into Salesforce 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 registerOne command installs the Deepline CLI and registers a workspace. Takes about 30 seconds. You only do this once per machine.
curl -s "https://code.deepline.com/api/v2/cli/install" | bash
deepline auth registerIn the Deepline dashboard, click Integrations → People Data Labs → paste your API key. Deepline uses PDL inside waterfalls and also directly via its dedicated search/enrich tools.
In the Deepline dashboard, click Integrations → Salesforce → Authorize. Salesforce opens its OAuth consent screen — pick sandbox or production, approve scopes. Deepline manages the refresh-token flow and JWT rotation every 55 minutes.
Open Claude Code and describe the workflow in plain English. Deepline handles the tool calls, waterfall routing, rate limits, auth refresh, and dedup. An example prompt for this pair:
> From PDL, find VPs of Finance at US companies with 501-5000 employees. Only keep matches where likelihood >= 9 (highest tier). Upsert into Salesforce as Leads using pdl_id as External_Id__c. Set LeadSource='PDL' and Industry from PDL's data.Once Claude's one-off run looks right, type "Deploy this as a workflow" and tell it the schedule. Deepline wraps the exact prompt + tool chain as a recurring workflow with run history, billing, and alerting in the dashboard.
> Deploy this as a workflow that runs every weekday morning at 8am.For 1,000 leads: $2.80
~0.28 credits per PDL match (likelihood 8+). Salesforce upsert is free on Enterprise. Deepline's credit pricing is pay-as-you-go — see code.deepline.com/docs/pricing for current rates.
Deepline tries the cheapest provider first and only falls back if it misses. For People Data Labs workflows, this means email enrichment stops at the first valid hit — you don't pay for the second and third provider unless you need to.
Once the one-off run looks right, "Deploy this as a workflow" wraps the same prompt + tool chain as a cron-scheduled workflow. Run history, per-run billing, and retry logic all live in the dashboard. No DevOps.
People Data Labs keys, Salesforce OAuth, waterfall fallbacks (Hunter, Dropcontact, Findymail, Prospeo) — all live in the Deepline dashboard. Rotate once; every workflow picks up the new credential automatically.
“Waterfall enrichment consistently delivers 80%+ match rates versus 35-50% from any single provider.”
“ZoomInfo pulled about 75% on its own, Apollo about 65%. A 4-provider waterfall landed at 88%.”
Citations sourced from community posts, vendor case studies, and engineering blogs.
Cause: People Data Labs credentials are either expired, revoked at the provider side, or the account tier doesn't expose API access.
Fix: Click the integration row in the dashboard → Test Connection. If it fails, re-paste the API key (or re-run OAuth for OAuth-based providers). Confirm the provider account tier includes API access — most providers gate this to paid tiers.
Cause: The filter returned 0 matches, OR rows failed a downstream gate (email not verified, already in destination, deliverability check failed).
Fix: Open the run in the Deepline dashboard → expand the step-by-step trace. Every row's path is logged: matched/unmatched at each stage. Most frequent culprit is the email-verification gate. Loosen the filter or remove the gate in the prompt if that's the cause.
Cause: Either hit a provider rate-limit, ran out of Deepline credits, or the destination API returned 500s Deepline classified as permanent.
Fix: Dashboard → Workflows → Recent Runs. Failed runs show the exact error and a "Replay" button. Credits are visible top-right. Rate-limit issues auto-resume once the window resets; permanent errors need intervention.
No. You need Claude Code (the CLI/IDE). Deepline provides the tool-execution layer and credit system. Your Claude Code subscription or Anthropic API key handles the LLM calls — Deepline handles the GTM actions underneath.
Built-in. For Salesforce as a destination, Deepline uses the provider-native idempotency key (email for HubSpot/Attio, External_Id for Salesforce, campaign-level dedup for Instantly/Smartlead/Lemlist). Reruns update existing records instead of creating duplicates.
Yes. Paste them in the Deepline dashboard under Integrations. Deepline uses your keys for the actual provider calls — you keep your provider contracts, billing, and rate limit allocation. Deepline's credit billing only covers the orchestration + waterfall layer.
Deepline runs exactly what you describe. The 1000 in cost-math is the reference cost per 1K rows — a 3-row run costs 3/1000 of that total. You never pay for rows that don't exist.
Yes. Mention it in the prompt — e.g. "If People Data Labs doesn't return an email, fall back to Hunter → Dropcontact → Findymail." Deepline assembles the waterfall automatically and charges you only for the provider that successfully finds each row.
Connect PDL and HubSpot in Deepline, describe your ICP in the chat, and Claude runs the full search + enrich + upsert. PDL's match confidence lands as a HubSpot custom property so sales views can prioritize by tier.
Connect PDL and Attio in Deepline, describe the ICP in plain English (or ES-DSL for power users), and Claude runs search + enrich + Attio upsert. matching_attribute=email_addresses keeps reruns idempotent.
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.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.