IntegrationEmail / Marketing destination
Mailchimp Integration - Route Signup and Lifecycle Events to Mailchimp
Meshes routes product events into Mailchimp through list membership changes. That gives lifecycle teams a cleaner way to start and stop sequences based on what happened in your product, not what eventually made it into a batch sync.
user.signuplesson.completedsubscription.cancelled|Actionsadd_to_listremove_from_listThe event names shown here are examples. In Meshes, event types are fully customized for each organization.
What you can do
Supported actions with real product context behind them
Create the Mailchimp connection in Meshes with an API key. Meshes loads the lists available to that Mailchimp account so rules can target real audiences without hardcoding IDs into your application.
Mailchimp is a common home for welcome and lifecycle email, but the real challenge is keeping audience state aligned with user behavior. When user.signup or lesson.completed happens, teams want the contact to enter the right list immediately.
Meshes keeps that routing in the product event layer. You create the Mailchimp connection in your Meshes workspace, choose the list action in the rule builder, and let Meshes handle delivery history, retries, and replay if a downstream error gets in the way.
add_to_listAdd subscribers to Mailchimp lists
Start welcome, nurture, or milestone email sequences when the product event means the user belongs in that audience now.
remove_from_listRemove subscribers from lists when the event changes state
Stop the old lifecycle path when the user converted, churned, or completed the experience that made that list relevant.
Common use cases
How Meshes teams usually put Mailchimp to work
These are the workflows where this destination tends to matter first. The point is to keep the product event, the destination action, and the operational retry path in one place.
Start welcome automation the moment a user signs up
Use user.signup to place the contact into the correct Mailchimp list without waiting for a manual export or separate sync process.
Trigger milestone email when learning progress changes
Use lesson.completed to move users into the next Mailchimp sequence as they cross product education milestones.
Keep lifecycle audiences driven from product state
Add or remove users from Mailchimp lists when activation, upgrade, or churn events change which lifecycle path fits them.
See the signup fan-out use caseAvoid duplicate list-management code across flows
Let Meshes keep Mailchimp membership changes close to the event stream instead of wiring them separately into every lifecycle job.
How it works
Connect the destination, define the rule, emit the event
In Meshes, the operating model is simple: create the connection in the workspace, create the rule, then let the event delivery layer handle the last mile.
Connect Mailchimp
Create the Mailchimp connection in Meshes with the API key and confirm the lists you want to target are visible in the connection action data.
Create routing rules in Meshes
Create rules for events like user.signup or lesson.completed, choose add_to_list or remove_from_list, and map the contact fields Mailchimp needs.
Emit the event and review delivery
Emit the event from your product or use Send Test Event in Meshes. Meshes delivers the list change, retries transient failures, and preserves the attempt log for replay.
Event example
Emit the product event once
import MeshesEventsClient from '@mesheshq/events';
const meshes = new MeshesEventsClient(
process.env.WORKSPACE_PUBLISHABLE_KEY!,
);
await meshes.emit({
event: 'lesson.completed',
resource: 'lesson',
resource_id: 'lesson_12',
payload: {
email: 'alex@northstar.io',
user_id: 'usr_2048',
lesson_id: 'lesson_12',
course_slug: 'activation-bootcamp',
},
});Connection model
API key
Create the Mailchimp connection in Meshes with an API key. Meshes loads the lists available to that Mailchimp account so rules can target real audiences without hardcoding IDs into your application.
Why Meshes
Why teams use Meshes for Mailchimp
The benefit is not just that the destination is supported. It is that the destination sits inside the same fan-out, retry, replay, and delivery-visibility layer as the rest of your stack.
List membership follows the event that actually matters
Welcome and lifecycle email works better when list changes happen from user.signup or lesson.completed, not from a separate export path.
Retries protect sequence entry points
If Mailchimp is temporarily unavailable, Meshes keeps the attempt visible and retryable instead of silently dropping the audience update.
Lifecycle routing stays reusable across workspaces
The same Meshes product event can power different Mailchimp accounts and rules across customer workspaces without changing your emission path.
You can fan out to more than email
That same event can also update CRM, support, or internal alerts in parallel so lifecycle messaging and the rest of the business stay aligned.
Keep exploring
Related guides, use cases, docs, and comparison pages
These links are the next layer down: concrete patterns, supporting documentation, and the build-vs-buy context that usually comes up during evaluation.
Catalog
All integrations
Return to the integrations catalog and compare Mailchimp with CRM, messaging, and webhook destinations.
Open linkDocs
Mailchimp docs
See the Meshes setup flow, supported actions, and rule-building details for Mailchimp.
Open linkUse Case
User signup fan-out
See how one signup event can update lifecycle email, CRM, support, and alerts at the same time.
Open linkGuide
Send signup events to Mailchimp
See how a Meshes rule can route user.signup into the right Mailchimp list for welcome automation.
Guide
Lesson completed to Mailchimp sequence
Use lesson.completed to move contacts into the next Mailchimp lifecycle path when they reach a real milestone.
Compare
Meshes vs. DIY
See what it takes to build Mailchimp list routing, retries, and replay logic into your own lifecycle stack.
Open link