Run BuiltWith Bulk Domain Job Result from Claude Code, route the signal-based selling output through Deepline, and write the reviewed result into Salesforce. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
BuiltWith to Salesforce is a supported Deepline workflow path for Claude Code. Use it when an agent needs to run BuiltWith, 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 BuiltWith to Salesforce with Claude Code?”
Source primitive
BuiltWith 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 BuiltWith 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 registerBuiltWith Technology signal → Deepline normalized run output
domain + technology, technology_id, domain, resolved_url, company_name, technology_name, category
Claude Code sees the technology signal as structured JSON, then Deepline adds provider name, action slug, run ID, retrieved timestamp, and row-level status.
Deepline normalized run output → Salesforce CRM contact
email, name, title, company, run ID, external ID, mapped enrichment fields
Use an external ID or domain/email key so reruns update existing records instead of creating duplicates.
Salesforce report, queue, or task 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 BuiltWith 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/builtwith.
Connect Salesforce as the destination. Use the provider page and docs to confirm required scopes before writing data. Destination reference: https://deepline.com/docs/providers/salesforce.
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 domain, technologies, detection timing plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=builtwith_bulk_domain_job_result:{"job_id":"{{job_id}}"}' --jsonAfter the pilot is correct, ask Claude Code to deploy the exact prompt as a Deepline workflow. The mapping from BuiltWith to Salesforce is preserved with run history, retries, billing visibility, and a rollback tag.
> Use BuiltWith Bulk Domain Job Result to find new buying signals for our target accounts, score each signal by urgency and fit, write the best technology signal into Salesforce, 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 BuiltWith action, run a pilot, inspect the output, and then write only reviewed rows to Salesforce.
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 BuiltWith 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 Salesforce 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 BuiltWith 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.
Use Deepline as a receiver for your Clay HTTP API column, then tell Claude to upsert each row into Salesforce Leads using the Clay row_id as External ID. Deepline handles OAuth refresh and rate-limit retries.
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 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.
Connect ZoomInfo and Salesforce in Deepline, describe the persona + firmographics, and Claude runs the full search + enrich + upsert. ZoomInfo's personId lives as External_Id__c for clean dedup.
Point Smartlead webhooks at Deepline, describe the routing rules, and Claude updates the matching Salesforce Lead + creates an Activity on every event.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.