Squarespace to Mailchimp, contacts synced via Sheets
Newsletter signups should feel like a win. Instead, they turn into a messy spreadsheet, a half-working integration, and that awkward “did we already import these?” moment. This Mailchimp contact sync problem shows up fast once you have real traffic.
Marketing managers hate it because the list stops being trustworthy. A studio owner feels it when leads go cold while you’re doing admin. And if you run an agency, the “quick import” becomes a recurring client headache.
This workflow pulls Squarespace newsletter submissions from Google Sheets and adds them to the Mailchimp audience you actually use. You’ll see how it works, what you need, and what to watch out for.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Squarespace to Mailchimp, contacts synced via Sheets
flowchart LR
subgraph sg0["Manual Start Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Manual Start Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Run Trigger", pos: "b", h: 48 }
n2@{ icon: "mdi:database", form: "rounded", label: "Retrieve Signup Sheet", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "Iterate Records Batch", pos: "b", h: 48 }
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/mailchimp.dark.svg' width='40' height='40' /></div><br/>Create Mailchimp Subscriber"]
n1 --> n2
n3 --> n4
n4 --> n3
n0 --> n2
n2 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0,n1 trigger
class n2 database
classDef customIcon fill:none,stroke:none
class n4 customIcon
The Problem: Squarespace Signups Don’t Land in the Right Mailchimp Audience
Squarespace can collect newsletter signups all day long, but getting those contacts into Mailchimp cleanly is where things get annoying. The native Squarespace → Mailchimp connection is limiting, and the moment you try to use an existing audience (the one with your segments, tags, and automations), you hit a wall. So you fall back to CSV exports, manual imports, and “just copy/paste it for now.” That “for now” tends to last months. Meanwhile, people who opted in don’t receive the welcome email, your campaign counts look off, and you start second-guessing your own list.
It adds up fast. Here’s where it breaks down in the real world.
- You end up doing CSV imports every week, which is easy to forget when things get busy.
- Duplicates slip in, so your audience size climbs but engagement quietly drops.
- Your main Mailchimp automations don’t fire because contacts never hit the correct audience.
- Small formatting issues (extra spaces, missing names) turn into manual cleanup right before a send.
The Solution: Sync Squarespace Signups from Sheets to Mailchimp
This n8n workflow uses Google Sheets as the “source of truth” for Squarespace newsletter submissions, then syncs new rows into Mailchimp as subscribers in the audience you choose. It can run on a schedule for continuous syncing, or you can trigger it manually whenever you want. Once it starts, it pulls the signup sheet, loops through each record in manageable batches, and creates a Mailchimp contact for each email address. The key benefit is simple: you stop treating email capture like a separate admin task. Signups flow into the list your business already runs on, without rebuilding your Mailchimp setup around Squarespace’s limitations.
The workflow starts with either a Scheduled trigger or a Manual trigger. Then n8n retrieves the Squarespace-connected Google Sheet, iterates through the rows, and sends each contact into Mailchimp as a new subscriber in your selected audience.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your Squarespace site brings in 20 newsletter signups a week. Manually, you might export a CSV, clean it, and import it to Mailchimp in about 30 minutes, then spend another 20 minutes fixing duplicates or formatting issues. Call it about 1 hour weekly, sometimes more during a promo. With this workflow, you schedule it to run daily: setup takes a few minutes, each run processes the new rows automatically, and you’re basically done unless something fails. That’s an hour you stop donating to busywork.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Squarespace to capture newsletter form submissions.
- Google Sheets to store new signup rows.
- Mailchimp API Key (get it from Mailchimp Account → Extras → API keys).
Skill level: Beginner. You’ll connect accounts, pick a spreadsheet, and select a Mailchimp audience.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A schedule (or a manual click) kicks things off. If you want “always-on” syncing, the Scheduled Run Trigger handles it. If you prefer control, you can run it manually after a campaign or content update.
Signups are pulled from Google Sheets. n8n reads the spreadsheet that Squarespace writes to when someone submits the newsletter block. Most teams keep columns like “Submitted On”, “Email Address”, and “Name”, but you can adapt it.
Each row gets processed in batches. The workflow loops over items so you don’t try to push a whole sheet at once. That’s helpful when your sheet has hundreds (or thousands) of rows.
Mailchimp gets updated with the right audience. For each signup, the workflow creates a subscriber in the Mailchimp audience you select by List Name or ID. This is the whole point: you keep your existing segments and automations intact.
You can easily modify which columns map into Mailchimp fields based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
This workflow can run on a schedule or manually for testing. Configure both triggers to control how the sync starts.
- Add and open Scheduled Run Trigger, then set your schedule rules for when the sync should run.
- Keep Manual Start Trigger connected to Retrieve Signup Sheet so you can run the workflow on demand while testing.
- Verify that Scheduled Run Trigger connects to Retrieve Signup Sheet as shown in the execution flow.
Step 2: Connect Google Sheets
Pull newsletter signups from Google Sheets so they can be synced to Mailchimp.
- Open Retrieve Signup Sheet and set Document to the correct spreadsheet ID (replace
[YOUR_ID]). - Set Sheet Name to
Sheet1(valuegid=0), or choose the sheet that holds your signup data. - Credential Required: Connect your googleSheetsOAuth2Api credentials.
Step 3: Set Up Batch Processing
Process each row in the signup sheet in controlled batches before sending to Mailchimp.
- Open Iterate Records Batch and keep default Options unless you need to change the batch size.
- Ensure Retrieve Signup Sheet outputs to Iterate Records Batch.
- Confirm the loop: Create Mailchimp Subscriber outputs back to Iterate Records Batch so all records are processed.
Step 4: Configure Mailchimp Subscriber Creation
Create or update Mailchimp subscribers using fields from each row in your sheet.
- Open Create Mailchimp Subscriber and set Email to
={{ $json['Email Address'] }}{{ $json.row_number }}. - Set Status to
subscribed. - Under Options, set Timestamp Signup to
={{ $json['Submitted On'] }}. - Under Merge Fields, set FNAME to
={{ $json.Name }}. - Credential Required: Connect your mailchimpApi credentials.
⚠️ Common Pitfall: The Email field includes {{ $json.row_number }}, which may create invalid email addresses. Remove it if you want to use the raw email value only.
Step 5: Test and Activate Your Workflow
Validate the data flow and ensure subscribers are created correctly before activating the schedule.
- Click Execute Workflow to run Manual Start Trigger and verify data is fetched from Retrieve Signup Sheet.
- Check that Iterate Records Batch loops through rows and Create Mailchimp Subscriber creates or updates subscribers.
- Confirm successful execution by reviewing Mailchimp for new subscribers and checking execution logs for errors.
- Activate the workflow to enable Scheduled Run Trigger for production syncing.
Common Gotchas
- Google Sheets credentials can expire or need specific permissions. If things break, check the Google connection inside n8n’s Credentials list first, then confirm the spreadsheet is shared with the right Google account.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Mailchimp can reject creates when the email already exists or when the audience requires double opt-in. Check the Mailchimp node’s execution output for the exact error, then adjust to “update if exists” behavior if your version supports it.
Frequently Asked Questions
About 30 minutes if your Sheet and audience are ready.
No. You’ll mostly connect accounts and choose the right spreadsheet and audience.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Mailchimp plan costs (API access is included on most paid plans).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, but plan to tweak the mapping. You can add columns in Google Sheets (like first name, consent source, or interest) and then map them in the Create Mailchimp Subscriber step to merge fields or tags. Common customizations include tagging by form, writing the signup date into a custom field, and skipping rows that don’t meet your consent rules.
Most of the time it’s an expired or wrong API key. Regenerate your Mailchimp API key, update it in n8n, and confirm you selected the correct audience (List ID mistakes are surprisingly common). If the email already exists, Mailchimp may throw an “already a list member” type error unless you switch the action to update/overwrite. Rate limits can show up too if you try to push a big historical sheet in one run.
A few thousand contacts is normal, and batching helps keep runs stable.
Often, yes, if you want control and predictability. Zapier and Make are great for quick two-step zaps, but this use case tends to grow: you’ll want batch processing, conditions, and better handling of “already exists” cases. n8n is also easier to self-host, which matters when you’re syncing daily and don’t want execution limits to become a bill you regret. The tradeoff is setup responsibility, especially if you self-host. If you want someone to sanity-check the best approach for your stack, Talk to an automation expert.
Once this is running, your Mailchimp audience stays current without the weekly import ritual. Set it up, let it sync, and get back to marketing that actually moves the needle.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
