Instantly to Pipedrive via n8n: Auto-Create Deals from Replies

Every RevOps team I work with hits the same dead zone. A rep gets a positive reply in Instantly, manually pastes the prospect into Pipedrive, and burns 20 to 40 minutes a day on data entry that a machine should handle in seconds. Worse, deals get created two days late or skipped entirely when that rep is on the road. This post is a concrete n8n workflow recipe that closes that gap, built specifically for teams running Instantly as their cold email engine and Pipedrive as their pipeline CRM.

Why This Gap Exists (and Why It Costs You Real Pipeline)

Instantly is purpose-built for cold outreach at volume. Pipedrive is purpose-built for pipeline management. Neither has a strong incentive to build a deep native integration with the other, so the handoff lands on your team. Most operators paper over it with a manual process, or worse, a one-size-fits-all Zapier zap that fires on every reply and floods Pipedrive with out-of-office messages and unsubscribes.

The smarter path is a filtered n8n workflow. n8n’s self-hosted architecture means your API keys stay on your infrastructure, the workflow logic is yours to version-control, and you are not paying per-task fees the moment volume picks up. I’ve deployed this exact stack for three SaaS clients in the last six months. It consistently cuts CRM lag from 24 to 48 hours down to under 15 minutes.

Setting Up the Workflow

Before you touch n8n, get two things ready: your Instantly API key (Settings > Integrations > API inside your Instantly workspace) and a Pipedrive API token (Settings > Personal Preferences > API). Store both in n8n’s built-in Credentials vault. Do not hardcode them in node parameters.

The workflow has four nodes. A Schedule Trigger, an HTTP Request node calling Instantly, an IF node filtering for positive replies, and a Pipedrive node creating the deal. That’s it. Four nodes, zero custom code required for the base version. Don’t let anyone talk you into starting with a more elaborate build.

The Timestamp Problem (and How to Solve It)

The trickiest part of the whole workflow is the since_timestamp parameter. Miscalculate it and you either miss replies or flood Pipedrive with duplicates from re-fetched history. I’ve watched this exact issue take down an otherwise solid build at a client who had been happily running 800 sequences a month.

// In an n8n Code node before the HTTP Request:
// Store last-run time in a static data variable
const workflowStaticData = $getWorkflowStaticData('global');

const lastRun = workflowStaticData.lastRunTimestamp
  || new Date(Date.now() - 10 * 60 * 1000).toISOString();

// Update for next execution
workflowStaticData.lastRunTimestamp = new Date().toISOString();

return [{ json: { since: lastRun } }];

This pattern uses n8n’s $getWorkflowStaticData('global') to persist the last successful run timestamp across executions. It is the correct solution, and it is buried in n8n’s static data docs rather than anywhere obvious in the UI. I’ve spent more time explaining this single concept to clients than any other part of the build combined.

Mapping the Instantly Payload to Pipedrive Fields

The Instantly reply payload gives you from_email, from_name, timestamp, campaign_name, reply_body, and lead_email. Here is exactly how I map those to Pipedrive:

• lead_email maps to Pipedrive Person email
• from_name parsed as first/last maps to Person name (split on the first space)
• campaign_name maps to a custom Pipedrive Deal field called “Source Campaign”
• reply_body (first 500 characters) maps to the Deal description or a linked Note
• A static value “Cold Reply” maps to a custom Deal label for pipeline filtering

The campaign name mapping is the one most people skip, and it’s the most operationally valuable. Reps can see exactly which sequence generated the reply. You can build Pipedrive reports that show pipeline contribution by Instantly campaign. That data starts justifying or killing campaigns within 60 days.

Which Teams Should Use This Stack

Who this Instantly + Pipedrive + n8n stack fits

Choose Instantly + Pipedrive + n8n if

• You send 500+ cold emails per month and reps are missing replies in their inbox
• Your CRM is Pipedrive and you do not want to migrate to HubSpot just to get automation
• You want self-hosted control over API keys and workflow logic without per-task fees

n8n self-hosted: free. Instantly from $37/mo. Pipedrive from $14/seat. Try n8n Free →

Choose Instantly + HubSpot + n8n if

• You are already on HubSpot and want to pull cold replies into existing contact records
• You need marketing attribution and lifecycle stage updates alongside deal creation
• Your team uses HubSpot sequences for warm follow-up after the cold reply converts

HubSpot from $15/seat. Workflow logic identical, just swap the Pipedrive nodes. Try HubSpot →

Choose Instantly + Zapier (no-code) if

• Your cold email volume is under 200 replies per month and per-task pricing is acceptable
• You need the workflow live in 30 minutes without touching code or hosting
• You are comfortable with Zapier's Instantly trigger (basic reply detection, no sentiment filter)

Zapier from $19.99/mo but tasks meter fast at volume. Try Instantly →

One Integration Recipe, Compounding Returns

This workflow is a foundation, not a ceiling. Once deals are flowing into Pipedrive automatically, you can layer in enrichment (pull company data via Clay before deal creation), routing logic (assign deals to different owners by campaign or territory), or a Slack notification so reps get a ping the moment a warm reply lands. The cold email to CRM handoff also connects directly to how deliverability affects reply rates, because a workflow that fires on 50 replies a day will fire on 12 if your domain health deteriorates.

Build the four-node version first. Verify it runs cleanly for a full week before extending it. Every client I’ve set this up for asks the same question around day ten: “Why didn’t we do this six months ago?”