Run LinkedIn Scraper Salesnavigator Extract Accounts List from Claude Code, route the signal-based selling output through Deepline, and write the reviewed result into HubSpot. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
LinkedIn Scraper to HubSpot is a supported Deepline workflow path for Claude Code. Use it when an agent needs to run LinkedIn Scraper, inspect the returned fields, and write the reviewed result into HubSpot with run history, retries, and explicit failure states.
Best query match
“How do I connect LinkedIn Scraper to HubSpot with Claude Code?”
Source primitive
LinkedIn Scraper returns structured fields that Deepline records with provider attribution and row-level status.
Destination primitive
HubSpot receives only reviewed rows after the pilot command succeeds.
This workflow moves data from LinkedIn Scraper into HubSpot 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 registerLinkedIn Scraper LinkedIn activity → Deepline normalized run output
post_url, activity_id, name, profile_url, headline, company
Claude Code sees the linkedin activity as structured JSON, then Deepline adds provider name, action slug, run ID, retrieved timestamp, and row-level status.
Deepline normalized run output → HubSpot CRM contact
email, name, title, company, run ID, email/domain key, source fields
Write only reviewed fields and keep provider output in a source-attribution property or timeline note.
HubSpot list, note, or task queue → 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 LinkedIn Scraper 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/linkedin_scraper.
Connect HubSpot as the destination. Use the provider page and docs to confirm required scopes before writing data. Destination reference: https://deepline.com/docs/providers/hubspot.
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 profile identity, post activity, company context plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv \
--with 'result=linkedin_scraper_salesnavigator_extract_accounts_list:{}' \
--rows 0:2 --json
# Review the pilot output, then map the result into HubSpot.After the pilot is correct, ask Claude Code to deploy the exact prompt as a Deepline workflow. The mapping from LinkedIn Scraper to HubSpot is preserved with run history, retries, billing visibility, and a rollback tag.
> Use LinkedIn Scraper Salesnavigator Extract Accounts List to find new buying signals for our target accounts, score each signal by urgency and fit, write the best linkedin activity into HubSpot, 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 LinkedIn Scraper action, run a pilot, inspect the output, and then write only reviewed rows to HubSpot.
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 LinkedIn Scraper 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 HubSpot 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 LinkedIn Scraper 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.
Subscribe Deepline to HubSpot's property-change webhook, then chat with Claude to define what happens when a field flips. Works as a drop-in upgrade for Clay webhook setups — same trigger, cheaper enrichment under the hood.
Connect ZoomInfo and HubSpot in Deepline, describe the accounts you want in plain English, and Claude pulls + enriches + upserts. Dedupes by domain so nightly runs never create duplicates.
Point Clay's HTTP API column at the Deepline webhook, tell Claude how to shape the HubSpot Contact, and Deepline handles the batched upsert. Works as a webhook receiver for any tool that POSTs JSON.
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.
Configure Instantly to send webhooks to Deepline, then tell Claude how each event should update the matching HubSpot Contact. Deepline verifies HMAC signatures and handles the Contact lookup automatically.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.