IntegrationEmail / Marketing destination
MailerLite Integration - Product Events in MailerLite Groups
Meshes routes product events into MailerLite through group membership changes. That gives lifecycle teams a direct path from product behavior to email segmentation without relying on delayed list cleanup or manual imports.
user.signuplesson.completedsubscription.cancelled|Actionsadd_to_groupremove_from_groupThe 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 MailerLite connection in Meshes with an API key. Meshes loads the available groups from that MailerLite account so rules can target current group IDs without hardcoding them into product code.
MailerLite groups are often the trigger surface for email segmentation and follow-up, but they only stay useful if product state reaches them reliably. Signup, milestone, and cancellation events usually matter more than whatever a weekly sync can reconstruct.
Meshes keeps that routing close to the event stream. A MailerLite connection with the API key lives in the workspace, the target group comes from live action data, and Meshes handles the delivery and observability path.
add_to_groupAdd subscribers to groups
Use signup and milestone events to place contacts into the groups that should drive the next MailerLite workflow.
remove_from_groupRemove subscribers from groups when state changes
Move contacts out of the old lifecycle path when cancellations, upgrades, or completions change which group is correct.
Common use cases
Where Meshes teams put MailerLite to work
Workflows where this destination tends to matter first — the product event, the destination action, and the operational retry path living inside the same workspace.
Onboarding email from signup events
Use user.signup to place the contact into the initial MailerLite group as soon as the account is created.
Users promoted into the next education segment
Use lesson.completed to move users into the group that matches the next step in the lifecycle journey.
Wrong sequences stopped when customer state changes
Use subscription.cancelled or downgrade events to remove subscribers from groups that no longer fit the lifecycle path.
Segmentation logic out of batch jobs
The same Meshes event stream that powers your other integrations can also keep MailerLite groups current in near real time.
How it works
Connection, rule, event — the three-step operating model
A connection lives in the workspace, a rule binds the event to the action, and the delivery layer handles the last mile with retries, replay, and per-destination history.
Connect MailerLite
Create the MailerLite connection in Meshes with the API key and confirm the groups you want are available in the action data for the connection.
Create routing rules in Meshes
Create rules for events like user.signup or lesson.completed, choose add_to_group or remove_from_group, and map the contact fields MailerLite needs.
Emit the event and review delivery
Emit the event from your app or use Send Test Event in Meshes. Meshes delivers the group change, retries transient errors, and preserves the attempt history 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',
course_slug: 'activation-bootcamp',
lesson_id: 'lesson_12',
},
});Connection model
API key
Create the MailerLite connection in Meshes with an API key. Meshes loads the available groups from that MailerLite account so rules can target current group IDs without hardcoding them into product code.
Why Meshes
Why teams use Meshes for MailerLite
MailerLite sits inside the same fan-out, retry, replay, and delivery-visibility layer as every other destination — customer-connected or internal — that the workspace owns.
Group routing stays tied to real product milestones
MailerLite segmentation becomes more useful when it starts from user.signup or lesson.completed instead of a delayed synchronization pass.
API-key setup stays isolated in the workspace
You can manage the MailerLite credential once in Meshes and reuse it across multiple routing rules without scattering it across services.
Retries protect lifecycle entry points
If the downstream API is transiently unavailable, Meshes keeps the attempt visible and retryable so you do not quietly lose the segment change.
The event can still fan out elsewhere
MailerLite can be one destination among several from the same event, so email does not drift away from CRM, support, or internal systems.
Keep exploring
Related guides, use cases, docs, and comparison pages
Concrete patterns, supporting documentation, and build-vs-buy context that usually come up during evaluation.
Catalog
All integrations
Return to the integrations catalog and compare MailerLite with the rest of the email and lifecycle-routing surface.
Open linkDocs
MailerLite docs
MailerLite setup steps, supported actions, and rule-building details.
Open linkUse Case
User signup fan-out
Example of a new signup updating lifecycle email and the rest of the GTM stack from the same event.
Open linkUse Case
Lesson completion flows
Example of milestone events driving the systems that need to react when users make real progress.
Open linkGuide
Routing guides
Destination-specific Meshes patterns that can be adapted for MailerLite routing rules.
Open linkCompare
Meshes vs. DIY
Breakdown of what it takes to own MailerLite group routing and lifecycle retry logic in custom code.
Open link