n8n’s marketing integration nodes connect directly to leading CRM and
email platforms—HubSpot, Salesforce, and Mailchimp—through a unified
resource‑operation model. HubSpot provides 25+ operations across contacts,
deals, companies, tickets, and engagements with OAuth2 or Private App
Token authentication. Salesforce exposes 18 triggers and 59 actions across
leads, accounts, contacts, opportunities, and custom objects, while
Mailchimp supports campaign management, audience list operations, and
subscriber sync through 14 actions and a webhook trigger.
[1]
[2]

How does the HubSpot node manage contacts, deals, and companies in n8n?

The HubSpot node provides comprehensive CRM operations: create, update,
delete, and get contacts, deals, companies, tickets, and engagements.
You authenticate via OAuth2 or a Private App Token (automatically
managed by n8n’s credential system under the HubSpot API scope), and
the node also supports searching leads by contact properties such as
lifecycle stage, hs_lead_status, and custom fields.
[3]

For deal association, connect a webhook trigger to HubSpot’s workflow
action “Send a webhook”—this fires when a deal reaches a stage or a
contact’s lifecycle stage changes. To associate a newly created contact
with a deal dynamically, use the HTTP Request node with the HubSpot
v4 associations API endpoint instead of the HubSpot node directly,
because the built‑in node’s “associate” operation does not accept dynamic
contact IDs in the Deal Association field as of early 2026. For the
complete pipeline pattern—intake → normalization → matching →
enrichment → CRM sync—see the
Lusha x n8n HubSpot enrichment guide.

What Salesforce triggers and actions are available in the n8n Salesforce node?

The Salesforce node provides 18 triggers monitoring new leads, updated
opportunities, and account changes in real time, plus 59 actions across
all major Salesforce objects—leads, accounts, contacts, opportunities,
cases, attachments, and custom objects—including create, update, delete,
get, search, and upload document operations with OAuth2 authentication.
[7]
[4]

Intelligent lead routing is a primary use case: n8n workflows can assign
accounts in real time based on territory, deal size, or external enrichment
from tools like Apollo or Pipedrive—going beyond Salesforce’s built‑in
assignment rules. Custom SOQL queries are supported through the node’s
search operation, enabling filtered data retrieval without writing raw
API calls. For lead enrichment patterns, combine Salesforce with
AI nodes for automated scoring and routing.

How does the Mailchimp node manage campaigns, audiences, and subscriber sync?

The Mailchimp node provides 14 actions—including creating, updating, and
deleting campaigns, managing audience list members, and retrieving list
groups—plus one webhook trigger for real‑time subscriber activity. The
Create Member action adds new subscribers to audience lists directly from
n8n workflows, with field mapping for email, first name, last name, and
custom merge fields.
[8]
[5]

A typical sequence: a Webhook or Form trigger feeds contact data into a
Mailchimp node, where you select the audience via List ID and map
subscriber fields. For personalized campaigns, you can chain a Set node
before Mailchimp to inject dynamic content like first name, company, or
custom merge tags. For automated
lead enrichment and scoring,
combine Mailchimp with the HTTP Request node to call external enrichment
APIs before the subscriber is added to a campaign.

How do webhook triggers connect CRM nodes to external form submissions and deal events?

Any HTML form, Typeform, Google Form, or Meta Lead Ad can POST to an n8n
Webhook trigger. The Webhook node’s Production URL is set in HubSpot’s
workflow action “Send a webhook,” Salesforce’s webhook destination, or a
third‑party form’s action attribute. n8n receives the structured payload
and a Set node maps field names to the CRM node’s expected API keys before
contact creation.
[2]
[9]

For HubSpot deal‑stage triggers, the webhook fires when a deal reaches a
configured stage; n8n can then update the deal, notify Slack, or push data
to an external analytics platform. For Salesforce, webhook‑based triggers
can fire on lead creation, opportunity stage changes, or case updates.
Always validate incoming data with a Set node before writing to the CRM;
for secure webhook hardening with HMAC signature verification, see the
n8n Webhook node configuration guide.

How do you build a lead enrichment pipeline with HubSpot, Salesforce, and AI nodes?

A five‑stage pipeline: Intake (webhook from forms, ads,
or Telegram captures leads), Normalization (Set node maps
fields and cleans formatting), Matching (IF node checks CRM
for duplicates by email), Enrichment (HTTP Request node
calls Clearbit, Lusha, or Apollo API), and CRM Sync
(HubSpot or Salesforce node pushes enriched contact with tagged source).
[10]

For AI‑powered enrichment, replace or augment the external enrichment API
with an OpenAI or Anthropic node that scores leads by fit and intent,
generates personalized outreach copy, and routes qualified leads to the
correct outbound sequence. The Lusha x n8n template demonstrates the full
pattern: Google Sheets & Telegram intake → Gemini normalization →
Lusha enrichment → HubSpot sync. For automated
order and fulfillment workflows,
switch the CRM node to an e‑commerce platform node after enrichment.

How do you route leads to the correct CRM queue or campaign based on score or source?

After enrichment, a Switch node reads the lead’s score tier (e.g., Hot,
Warm, Cold) or source channel (Web, Chat, Email, Ad) and routes high‑
intent leads to a Salesforce queue or HubSpot deal pipeline via the
respective CRM node’s create/update operation. For Salesforce, set the
OwnerId field to the target queue; for HubSpot, assign the
deal stage and owner.
[9]
[11]

For campaign‑based routing, use the Mailchimp node to add scored leads to
different audiences or tag them with custom merge fields. A scheduled
workflow can check the CRM every hour for new leads not yet contacted and
send them a personalized first email via the Gmail or SMTP node. Queue IDs
and campaign IDs are stored as workflow variables ($vars) for
easy maintenance. For designing scalable branching architectures with
bitmasking, see the
IF & Switch node branching guide.