Sync Mailchimp unsubscribes with HubSpot CRM, Slack, Google Sheets and Gmail
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 12 nodes and runs on Mailchimp events (unsubscribe). Along the way it connects Mailchimp, Slack, Google Sheets and Gmail. It also calls api.hubapi.com over HTTP.
How it runs
Trigger: On Mailchimp events (unsubscribe).
- Set - Normalize & Enrich Data (Code): runs custom JavaScript code
- HubSpot - Search Contact by Email (HTTP Request): calls api.hubapi.com (POST)
- Send a confirmation email (Gmail): uses Gmail
- If: checks a condition and branches into true / false
- Update HubSpot Contact (HTTP Request): calls an HTTP API (PATCH)
- Create HubSpot Contact (HTTP Request): calls an HTTP API (POST)
- Set - Prepare Slack Payload (Edit Fields (Set)): sets 9 fields: hubspotContactId, hubspotPortalId, email…
- Slack: uses Slack
- Slack: uses Slack
- Store Unsubscribe Details in Sheet (Google Sheets): append
…plus 1 more step. See the full node list below.
Services it uses
HTTP calls to: api.hubapi.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Mailchimp Trigger
n8n-nodes-base.mailchimpTrigger - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Slack
n8n-nodes-base.slack - Google Sheets
n8n-nodes-base.googleSheets - Gmail
n8n-nodes-base.gmail - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if
From the author
How it works This workflow automatically handles every Mailchimp unsubscribe event by capturing the contact details, syncing the status to HubSpot, alerting the team on Slack, logging the record to Google Sheets, and sending the user a confirmation email —…