Import guide
Import Mailchimp audience members into monday.com on a schedule
Marketing teams keep campaign data in Mailchimp and the work that follows in monday.com: follow-ups, events, partner outreach. Today the join between the two is a CSV export.
Boardfeed reads an audience and its merge fields on a schedule and keeps a board in step with it, using the email address as the key so subscribers update rather than accumulate.
Doing it by hand, every time
- Export the audience as a CSV from Mailchimp.
- Import it into the board and re-map the merge fields.
- Lose the custom merge fields that came out as unnamed columns.
- Repeat next week, and decide whether to delete the previous rows first.
The scheduled route
- Connect Mailchimp with an API key — read-only access to the audiences you select.
- Map the member fields and the merge fields you care about to board columns.
- Use the email address as the upsert key so a subscriber who changes status updates their item instead of creating a second one.
- Run it daily, weekly, or on demand before a campaign meeting.
Field mapping notes for Mailchimp
This is the part that decides whether an import works on the first try. Everything below is handled in the mapping step, before a run is scheduled.
- Merge fields: every audience defines its own, so the field list is read from the account rather than assumed. Unsubscribed members keep their merge field values.
- Status: subscribed, unsubscribed, cleaned, pending and archived come through as separate values, which map cleanly to a status column.
- Tags and groups: returned as lists, so they map to a dropdown or a text column rather than a single-select status.
- Dates: opt-in timestamps are ISO-8601 and map directly to a date column.
- Key column: email is the natural key. If two contacts share an address, the later record wins.
Mailchimp import questions
- Does this write anything back to Mailchimp?
- No. The connection is read-only. Boardfeed imports from Mailchimp and never edits your audience.
- Are unsubscribed contacts imported?
- That is your choice. Choose which statuses to include; many teams import everyone and show the status on the board so the change is visible.
- Which key should I use for upsert?
- Email, for member-level rows. If you are importing events or campaign activity rather than people, use the record’s own id and see the REST API guide for the same pattern.