Smartlead and n8n integration: full setup walkthrough for 2026

How Smartlead and n8n Connect

Smartlead sends real-time webhook events to n8n when a lead replies, opens an email, clicks a link, or completes a sequence. n8n can write back to Smartlead via REST API to add contacts, update custom fields, or move leads between campaigns. The connection requires no native plugin and works on any Smartlead paid plan.

On the inbound side, Smartlead's webhook system POSTs a JSON payload to your n8n webhook URL within seconds of an event firing. On the outbound side, you use n8n's HTTP Request node to call Smartlead's v1 API. That's the full architecture: webhooks in, REST calls out.

The community n8n node for Smartlead handles authentication automatically once you enter your API key. For advanced use cases like filtering by campaign or splitting traffic across multiple Smartlead accounts, you'll work directly with the HTTP Request node instead. The community node covers 80% of what most teams need.

Step-by-Step Setup Guide

Setting up the Smartlead and n8n integration takes about 20 minutes if your API credentials are ready. You'll configure an n8n webhook to receive Smartlead events, then add HTTP Request nodes for outbound API calls. No paid n8n plan is required for basic automation on self-hosted instances.

1. Get your Smartlead API key. Log into Smartlead, go to Settings, and copy your API key from the API section. You'll need it in every outbound HTTP Request node.
2. Install or access n8n. Self-hosted: run npx n8n or pull the official Docker image. Cloud: log into n8n Cloud and open a new workflow. Self-hosting is the right call for most outreach teams.
3. Add a Webhook trigger node in n8n. In your new workflow, add a Webhook node. Set the HTTP method to POST and copy the generated webhook URL. Turn on "Respond Immediately" to avoid Smartlead timeout errors.
4. Register the webhook URL in Smartlead. In Smartlead, navigate to Settings, then Webhooks. Paste your n8n URL and select the events you want: reply, open, click, bounce, or unsubscribe. Save and activate.
5. Add processing nodes in n8n. After the webhook trigger, add a Set node to extract the fields you need (email, campaign ID, reply text). Route that data to your CRM, Slack, or spreadsheet using n8n's built-in nodes.
6. Test with a live event. Use Smartlead's "Test Webhook" button to send a sample payload. Confirm it arrives in your n8n execution log with the expected structure before activating in production.

Don't wait for slow downstream nodes to complete before acknowledging the webhook. Add a "Respond to Webhook" node immediately after the trigger, set it to return 200, and run the rest of your workflow asynchronously. Smartlead drops the connection if you take more than 5 seconds to respond.

What You Can Automate With This Integration

The highest-ROI automations push enriched leads from a data provider into Smartlead campaigns without manual CSV imports and pull reply data back into your CRM to update deal stages. Teams running 500+ new contacts per week typically save 8 to 12 hours of manual work per month from these two workflows alone.

Auto-Enroll Leads From Your CRM

When a deal reaches a specific stage in HubSpot or Pipedrive, an n8n workflow adds that contact to a Smartlead campaign automatically. You map the CRM fields to Smartlead's lead object once, and every qualifying deal enrolls within seconds of the stage change. No CSV exports, no manual uploads, no copy-paste errors.

Update Your CRM on Reply

When Smartlead fires a reply event, n8n routes it to your CRM to log the activity and update the contact's status. Add a Slack alerting node, and your team gets notified in the right channel within 30 seconds of a warm reply. That's a real improvement in response time, not a marginal one.

Suppress Unsubscribes Across Every Tool

Smartlead's unsubscribe webhook is the one most teams overlook. Wire it to n8n and you suppress that contact across every tool at once: remove from your data provider lists, add to a HubSpot suppression list, archive in your tracking spreadsheet. Doing this manually across three tools takes 5 minutes per contact. Automated, it takes zero.

Troubleshooting Common Failures

The two most common failures are webhook timeouts from Smartlead (caused by slow n8n response times) and 401 errors on API writes (expired or wrong-scope API keys). Both are fixable in under 10 minutes if you know where to look.

Webhook Timeouts

Smartlead drops the connection if your endpoint doesn't respond within 5 seconds. Add a "Respond to Webhook" node immediately after the trigger, set it to return 200, and let the rest of your workflow run after that point. n8n handles this natively. Don't put a database write or an AI call before the acknowledgment.

401 Unauthorized Errors on API Calls

This almost always means you've pasted the wrong API key or the key was regenerated in Smartlead's settings. Check Settings > API in Smartlead for your current key. Use n8n's credential store rather than hardcoding the key in the node so a single update propagates everywhere at once.

Missing Fields in Webhook Payloads

Smartlead's payload structure differs by event type. A reply event includes the reply text and sender details. An open event doesn't. Add an IF node after the webhook trigger to branch on event_type before accessing fields that only exist in specific payloads. Skipping this step causes null reference errors that are annoying to debug.

Duplicate Records in Your CRM

If you're adding leads to Smartlead from multiple sources and syncing replies back to your CRM, you'll hit duplicate contact creation. Fix it with a search-before-write pattern: query your CRM by email first, then update if found rather than always creating new. This applies to HubSpot, Salesforce, and Pipedrive alike.

Pricing and Plan Requirements

Smartlead's webhook functionality is available on all paid plans, starting at $39/month for the Basic plan. n8n is free to self-host with no workflow execution limits. n8n Cloud starts at $20/month if you'd rather skip infrastructure management. You need no enterprise add-ons to run this integration at full capacity.

The Smartlead API enforces rate limits per plan tier. Basic plan accounts are capped at 10 API requests per second. If you're batch-importing thousands of leads via n8n, add a Wait node between batches to stay inside that limit. Pro and higher plans get increased rate limits that make large batch imports much faster.

The only reason to pay for n8n Cloud over self-hosting is if no one on your team can run a Docker container. For everyone else, self-hosting gives you unlimited executions, full log access, and no per-workflow pricing surprises as you scale.

For teams that want managed outreach without building these workflows themselves, Modern Inbound's Research-Led Outreach handles the full stack: account lists, campaign setup, deliverability, and reply routing.

Scale Outreach Without Hiring SDRs

Most B2B teams underestimate the work before sending: buyer-language research, list logic, DNS, warm-up, deliverability, copy testing, and reply handling. Modern Inbound runs the operating layer so founders can stay focused on sales calls.

Frequently Asked Questions

Does this integration work with Smartlead's multi-sender setup?

Yes. Smartlead fires webhook events regardless of which sending account triggered them. The payload includes the sender's email address, so you can filter in n8n by sender if you need to route events differently per inbox. No additional configuration is required in Smartlead.

Can n8n handle high webhook volume from Smartlead without dropping events?

Self-hosted n8n with adequate server resources handles thousands of events per hour without issue. The bottleneck is usually your downstream tools (CRM API rate limits, Slack message limits) rather than n8n itself. For very high volume, use n8n's queue mode with a Redis backend.

Is the Smartlead API key the same as the webhook secret?

No. The API key authenticates your outbound calls to Smartlead's REST API. Smartlead doesn't currently sign webhook payloads with a secret by default. You can add IP allowlisting in n8n to restrict which sources can trigger your webhook URL as a basic security measure.

Should I use the n8n Smartlead community node or the HTTP Request node?

The community node is faster to set up for standard operations like adding leads or updating statuses. The HTTP Request node gives you access to every Smartlead API endpoint, including ones the community node doesn't yet cover. Start with the community node and switch to HTTP Request when you hit its limits.