Run Icypeas Find Company Url from Claude Code, route the signal-based selling output through Deepline, and write the reviewed result into Lemlist. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider-doc links.
Icypeas to Lemlist is a supported Deepline workflow path for Claude Code. Use it when an agent needs to run Icypeas, inspect the returned fields, and write the reviewed result into Lemlist with run history, retries, and explicit failure states.
Best query match
“How do I connect Icypeas to Lemlist with Claude Code?”
Source primitive
Icypeas returns structured fields that Deepline records with provider attribution and row-level status.
Destination primitive
Lemlist receives only reviewed rows after the pilot command succeeds.
This workflow moves data from Icypeas into Lemlist 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 registerIcypeas Person → Deepline normalized run output
email, linkedin_url, id, url, domain, or provider key
Claude Code sees the person as structured JSON, then Deepline adds provider name, action slug, run ID, retrieved timestamp, and row-level status.
Deepline normalized run output → Lemlist Campaign lead
email, name, company, campaign_id, run ID, personalization variables
Map only reviewed personalization fields to avoid sending raw provider text directly.
Lemlist campaign lead 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 Icypeas 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/icypeas.
Connect Lemlist as the destination. Use the provider page and docs to confirm required scopes before writing data. Destination reference: https://deepline.com/docs/providers/lemlist.
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=icypeas_find_company_url:{"companyOrDomain":"{{companyOrDomain}}"}' --jsonAfter the pilot is correct, ask Claude Code to deploy the exact prompt as a Deepline workflow. The mapping from Icypeas to Lemlist is preserved with run history, retries, billing visibility, and a rollback tag.
> Use Icypeas Find Company Url to find new buying signals for our target accounts, score each signal by urgency and fit, write the best person into Lemlist, 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 Icypeas action, run a pilot, inspect the output, and then write only reviewed rows to Lemlist.
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 Icypeas 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 Lemlist 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 Icypeas 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.
Connect the LinkedIn scraper and Lemlist in Deepline, paste a post URL into the chat, and Claude scrapes commenters, runs the email waterfall, generates first lines, and drops everyone into your Lemlist campaign.
Point Lemlist at Deepline's webhook, tell Claude how to handle each channel (email vs LinkedIn), and HubSpot Contacts update with channel-tagged activity automatically.
Connect Apollo and Lemlist in Deepline, describe the filter, and Claude pulls + verifies + imports. Lemlist's multi-channel sequences (email + LinkedIn) pair naturally with Apollo's firmographic filters.
Point Lemlist at Deepline, tell Claude how each channel event maps to Salesforce, and Deepline handles the routing + OAuth refresh.
Connect HubSpot and Lemlist in Deepline, describe the segment, and Claude pushes with hubspot_contact_id tagged so replies route back to the right Contact.
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.