Run Parallel Run Task from Claude Code, route the signal-based selling output through Deepline, and write the reviewed result into Linear. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
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 Parallel 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/parallel.
Connect Linear as the destination. Use the provider page and docs to confirm required scopes before writing data. Destination reference: https://deepline.com/docs/providers/linear.
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 research task, structured finding, citation bundle plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=parallel_run_task:{"input":"{{input}}"}' --jsonAfter the pilot is correct, ask Claude Code to deploy the exact prompt as a Deepline workflow. The mapping from Parallel to Linear is preserved with run history, retries, billing visibility, and a rollback tag.
> Use Parallel Run Task to find new buying signals for our target accounts, score each signal by urgency and fit, write the best web result into Linear, 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 Parallel action, run a pilot, inspect the output, and then write only reviewed rows to Linear.
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 Parallel 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 Linear 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 Parallel 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.
Run BuiltWith Free Lookup from Claude Code, route the signal-based selling output through Deepline, and write the reviewed result into Linear. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
Run BuiltWith Trends from Claude Code, route the SEO and AEO research output through Deepline, and write the reviewed result into Linear. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
Run Icypeas Find Company Url from Claude Code, route the signal-based selling output through Deepline, and write the reviewed result into Linear. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
Run Crustdata Job Listings from Claude Code, route the signal-based selling output through Deepline, and write the reviewed result into Linear. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
Run Deepline Native Company To Contact By Role Waterfall from Claude Code, route the signal-based selling output through Deepline, and write the reviewed result into Linear. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.