Skip to content
Automation Squad
AtMcSMade to order

Marketing & content publishing

Airtable newsletter calendar → Mailchimp campaign + test email + Slack

Mark the issue Ready in Airtable and the Mailchimp campaign builds and test-sends itself.

The newsletter is written in Airtable but assembled by hand in Mailchimp, every issue. This flow does the assembly. When a record's status changes to Ready, the rich-text body becomes HTML, a Mailchimp campaign is created with the subject, preview text and audience from the record, and a test email goes to the reviewers listed on it. Slack gets the edit link, and sending stays a human decision.

How it works

  1. At

    Trigger

    Record updated in the Issues table (polled on a Last modified time field)

    Airtable

  2. if

    Step 1

    Filter to records marked Ready

    Only records whose Status is Ready and whose Campaign ID is empty continue. Editing a record mid-draft does nothing.

  3. if

    Step 2

    Convert the body to HTML

    Airtable returns the rich-text Body field as markdown; n8n's Markdown node turns it into HTML, and the subject, preview text, from name and reviewer addresses are read from the record.

  4. Mc

    Step 3

    Create the campaign

    A regular campaign is created in Mailchimp through its REST API, with the audience, subject line, preview text, from name and reply-to taken from the record.

  5. Mc

    Step 4

    Set the campaign content

    HTML goes in as the campaign body, wrapped in a plain HTML shell you edit once so header and footer match earlier issues.

  6. Mc

    Step 5

    Send the test email

    Mailchimp's test-send endpoint emails the campaign to the reviewer addresses on the record, subject prefixed [Test] by Mailchimp.

  7. At

    Step 6

    Write the campaign details back

    The record receives the Mailchimp campaign ID, an edit link built from the campaign's web ID, the time, and Status set to Test sent.

  8. S

    Step 7

    Tell the channel

    Your marketing channel gets a message naming the issue, linking to the campaign in Mailchimp and listing who received the test.

What changes once it runs

  • A Mailchimp campaign exists, with content and settings filled, within a couple of minutes of the record being marked Ready on a one-minute poll.
  • Reviewers get a real test email in their inbox rather than a link to a draft in a tool they do not use.
  • Subject line, preview text and audience are set from the record, so none of them can be forgotten in the Mailchimp editor.
  • The record holds the campaign ID and edit link, so Airtable stays the one place the team looks.
  • No campaign is sent by the workflow. The send button in Mailchimp is still yours.

What you get

  • The n8n workflow export with all three Mailchimp API calls configured
  • An Airtable base template with the Issues table, its fields and two example records
  • HTML shell the body is wrapped in, with the header and footer blocks marked for your branding
  • A setup guide covering the Mailchimp API key, audience ID and Slack channel
  • Recorded walkthrough from Ready to a test email in the inbox

Before you start

  • An Airtable base with an Issues table: Subject, Preview, Body (rich text), Reviewers, Status and a Last modified time field (template included)
  • Mailchimp account with an API key and at least one audience (the Free plan is enough for creating and test-sending)
  • A Slack workspace where n8n's Slack app is allowed to post to the channel
  • n8n instance with Airtable, Mailchimp and Slack credentials connected

Built for

Questions before you buy

Can it schedule or send the campaign too?
It can, and the package shows where. A Send at field on the record can drive Mailchimp's schedule call if your plan allows scheduling. We ship it switched off, because a test email nobody read before an automatic send is how mistakes reach the whole list.
Why write in Airtable rather than Mailchimp's editor?
Because the writing happens where the calendar is. Airtable's rich text field comes out of the API as markdown, with headings, links and lists, and n8n converts it to HTML in one node. Images are the exception: paste them into the HTML shell or add them in Mailchimp before sending. If your team prefers to write inside Mailchimp, this is the wrong package.
What happens if a Mailchimp call fails?
The record's Status is set to Error with the message Mailchimp returned, and Slack gets the same message. If the content or test-send step fails after the campaign was created, the campaign ID is still written back, so you can open it in Mailchimp and finish by hand.
Does it run on Make or Zapier?
Not as shipped. The content and test-send steps call Mailchimp's REST API directly, and the package is built and tested for n8n only. Ask before buying if you need it elsewhere.
Does polling Airtable need a paid Airtable plan?
That depends on how often you poll. Airtable's Free plan allows 1,000 API calls a month and a one-minute poll uses about 43,000, so on Free set the poll to hourly, which uses about 720. Team plans allow 100,000 a month and can poll every minute.

Nearby on the shelf

Whole catalog