How to integrate Instantly with n8n in 2026

What This Integration Actually Does

Instantly and n8n connect through Instantly's REST API and outbound webhook system. When a campaign event fires, such as a reply received, a bounce, or a meeting booked, n8n catches it via a Webhook node and runs whatever logic you've built. Data flows one way by default from Instantly to n8n, but you can push contacts into Instantly campaigns from n8n too. The sync is near-real-time, typically completing in under 30 seconds.

The integration isn't native. You won't find n8n listed in Instantly's integrations tab. You're wiring them together manually using Instantly's webhook settings and n8n's HTTP Request and Webhook nodes, which gives you full control over what triggers, what gets filtered, and where data lands.

n8n is the better tool here than Zapier. Zapier charges per task and restricts logic branching on lower plans. n8n lets you build conditional routing, loops, and multi-step error handling in the same workflow for a flat monthly rate, or for free if you self-host. That's not a close call.

How to Set Up the Instantly and n8n Integration

Setting up this integration takes about 20 minutes if you have an active Instantly account and an n8n instance running. You need an Instantly API key, a webhook URL from n8n, and a basic understanding of n8n node configuration. No code is required for standard workflows.

1. Generate your Instantly API key. Go to Instantly Settings, click API Keys, and create a new key. Copy it somewhere safe. You'll need it in n8n's HTTP Request nodes when pushing data back into Instantly.
2. Create a new workflow in n8n. Open your n8n instance, click New Workflow, and give it a descriptive name like Instantly Reply Handler. Start with a blank canvas.
3. Add a Webhook trigger node. Drag a Webhook node onto the canvas and set the HTTP method to POST. n8n generates a unique webhook URL automatically. Copy it.
4. Configure Instantly's webhook settings. In Instantly, go to Settings, then Webhooks. Paste the n8n URL into the endpoint field. Select which events trigger it: replies, bounces, unsubscribes, or all events. Save.
5. Map the payload fields. Send a test event from Instantly to activate the webhook in n8n's test mode. Once n8n receives it, you'll see the full payload structure. Wire the fields you need, such as lead email, campaign ID, and reply text, to your downstream nodes.
6. Set the workflow to Active. A workflow left in test mode only accepts manual test calls. Switch it to Active before treating the integration as live. This step is the most commonly skipped.

Workflows You Can Build Today

The most valuable workflows from this integration handle reply routing, lead stage updates, and outbound lead sync. Teams running these patterns report cutting 4-6 hours of weekly manual admin. Three use cases cover most outbound setups without overcomplicating the automation layer.

Reply to CRM Stage Update

When a lead replies in Instantly, n8n catches the webhook, scans the reply for keywords like 'interested' or 'next week', and updates the deal stage in HubSpot or Salesforce. You can route the notification to a specific AE's Slack channel based on account owner field. One workflow replaces 10-15 minutes of manual processing per reply.

Bounce Handling and Data Cleanup

Instantly marks a contact as bounced. n8n receives that event, finds the matching CRM record, tags it as an invalid email, and can trigger a re-verification pass. This keeps your database clean without a manual scrub after every campaign run. It also prevents re-enrolling bad addresses in future sequences.

CRM-to-Campaign Lead Sync

Run the flow in reverse. When a lead hits a trigger stage in your CRM, n8n fires an HTTP Request to Instantly's POST /contacts/upload endpoint and drops that contact into an active sequence. No CSV exports. No manual uploads. If you want this running hands-free from day one, Modern Inbound's outreach team builds and manages this stack for clients who don't want to touch the automation layer themselves.

Troubleshooting Common Setup Failures

Most Instantly and n8n integration problems trace back to four root causes: incorrect webhook URL format, missing authentication headers, outdated payload field paths, and a workflow stuck in test mode. Each has a straightforward fix once you know where to look.

Webhook Not Receiving Events

Check that your n8n workflow is set to Active. Inactive workflows don't accept production webhook calls; they only respond to manual test triggers. This is the single most common reason the integration appears broken right after setup, and it's fixed in seconds.

401 Errors When Pushing Data to Instantly

Instantly's API requires your key in the Authorization header as a Bearer token. If you're seeing a 401 from an HTTP Request node, you've likely added the key as a query parameter instead. Move it to the header field, formatted as: Bearer YOUR_KEY_HERE. Query-parameter authentication isn't supported.

Lead Email Arriving as Null

Instantly changed its webhook payload structure in early 2025. The lead email now sits at lead.email, not at the root email field. If your workflow template predates that change, your field mappings return null values. Update them before debugging anything else.

Execution Delays Over 2 Minutes

n8n Cloud workflows on the Starter plan cold-start with a 1-2 minute delay when the workflow hasn't fired recently. If reply routing feels slow, upgrade to a plan with always-on execution, or run n8n on a self-hosted VPS where there's no cold-start penalty at all.

Pricing and Plan Requirements

You need Instantly Growth at $37/month or higher for API and webhook access. n8n Cloud starts at $20/month for 2,500 executions per month. Self-hosted n8n is free but requires a persistent VPS to run reliably. Entry cost runs $57/month combined, which is less than most standalone automation platforms charge for the same data-routing capability.

Instantly Growth covers up to 1,000 active leads with full API access. Hypergrowth adds higher lead limits with the same integration features. On the n8n side, the Starter plan handles most outbound automation volumes. Teams processing more than 5,000 webhook events per month should look at n8n Pro before hitting execution caps mid-campaign.

Instantly's API rate limit sits at 10 requests per second on Growth. n8n queues requests automatically, so you're unlikely to hit it unless you're running bulk contact imports at the same time as live campaign event processing.

Frequently Asked Questions