Skip to main content

Sync Mailchimp unsubscribes with HubSpot CRM, Slack, Google Sheets and Gmail

Workflow preview

Workflow preview
100%
Sync Mailchimp unsubscribes with HubSpot CRM, Slack, Google Sheets and Gmail preview
Open on n8n.io

1. Workflow Overview

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...

Best for

  • Social Media automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.mailchimptrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.slack, n8n-nodes-base.googlesheets, n8n-nodes-base.gmail, n8n-nodes-base.set

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Avkash Kakdiya.

Original n8n.io source

1.1 Workflow description

Title
Sync Mailchimp unsubscribes with HubSpot CRM, Slack, Google Sheets and Gmail
Workflow name
Sync Mailchimp unsubscribes with HubSpot CRM, Slack, Google Sheets and Gmail

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 — all without any manual effort.

Step-by-step

  • Trigger & normalize

  • Mailchimp — Unsubscribe Trigger – Listens for unsubscribe events on a Mailchimp audience list.

  • Set — Normalize & Enrich Data – Parses and normalizes the raw Mailchimp payload across all supported formats, extracting email, first name, last name, phone, address, list name, unsubscribe reason, campaign ID, member rating, and formatted timestamps.

  • CRM sync

  • HubSpot — Search Contact by Email – Searches HubSpot for an existing contact matching the unsubscribed email address.

  • IF — Contact Exists in HubSpot? – Routes to update or create based on whether a matching contact is found.

  • Update HubSpot Contact – Marks the existing contact as Unsubscribed, sets the email opt-out flag, and records the unsubscribe source, date, reason, campaign ID, and Mailchimp list ID.

  • Create HubSpot Contact – Creates a new HubSpot contact with full unsubscribe details and opt-out status if no existing contact is found.

  • Payload preparation

  • Set — Prepare Slack Payload – Consolidates the HubSpot contact ID with all normalized unsubscribe data into a single clean object for downstream nodes.

  • Team notifications

  • Slack — Alert – Posts an instant unsubscribe alert to the marketing Slack channel with the contact's name, email, audience, and timestamp.

  • Slack — Log to – Posts a detailed CRM audit log entry including HubSpot contact ID, campaign ID, unsubscribe reason, and processing timestamp.

  • Logging & confirmation

  • Store Unsubscribe Details in Sheet – Appends a full unsubscribe record to Google Sheets including email, name, audience, reason, campaign ID, HubSpot contact ID, member rating, and timestamp.

  • Send a confirmation email – Sends a plain-text Gmail confirmation to the unsubscribed user acknowledging their removal from the list.

  • Completion log

  • Set — Workflow Completion Log – Records a final summary of all completed actions, processing timestamp, and workflow status for monitoring and audit purposes.

Why use this?

  • Instantly syncs every Mailchimp unsubscribe to HubSpot so CRM contact status is always accurate and compliant
  • Automatically creates new HubSpot contacts for unsubscribers who don't yet exist in the CRM
  • Keeps the marketing team informed in real time with Slack alerts and a separate audit log channel
  • Logs every unsubscribe event to Google Sheets for trend analysis, compliance reporting, and list health tracking
  • Sends users an automatic confirmation email so every unsubscribe request is professionally acknowledged

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note7

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Sticky Note8

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Sticky Note9

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Sticky Note10

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Sticky Note11

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Sticky Note12

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - Sticky Note13

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 8 - Mailchimp - Unsubscribe Trigger

Type / Role
n8n-nodes-base.mailchimpTrigger - mailchimpTrigger
Config choices
Version 1

Block 9 - Set - Normalize & Enrich Data

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 10 - Update HubSpot Contact

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 11 - Create HubSpot Contact

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 12 - Slack - Alert

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 13 - Slack - Log to

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 14 - Store Unsubscribe Details in Sheet

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.7

Block 15 - Send a confirmation email

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.2

Block 16 - Set - Workflow Completion Log

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 17 - Set - Prepare Slack Payload

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 18 - IF - Contact Exists in HubSpot?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 19 - HubSpot - Search Contact by Email

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

3. Summary Table

Workflow Sync Mailchimp unsubscribes with HubSpot CRM, Slack, Google Sheets and Gmail
Complexity advanced
Nodes 19
Categories Social Media
Author Avkash Kakdiya
Published 21 May 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15875/15875.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Sync Mailchimp unsubscribes with HubSpot CRM, Slack, Google Sheets and Gmail do?

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...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Social Media use case.