WorkflowCourse progress workflow

Send Lesson Completion Events to Mailchimp Sequences

Use Meshes to route `lesson.completed` into the Mailchimp audience or list state that should own the next email, whether that means the next lesson, a module recap, a milestone reminder, or a completion push.

Event signal:lesson.completed| Destination:Mailchimp| Use case:Lesson Completion Flows| Typical setup:~15 minutes

Workflow outcome

The product event is small. The downstream effect is not.

The workflow begins with one lesson.completed event from your course product and ends with the learner inside the Mailchimp audience state that should trigger the next relevant sequence.

That replaces generic drip timing with behavior-based timing. Instead of hoping the student is ready when the next email is scheduled, the email path starts because the lesson was actually completed.

Why teams care

This is the kind of workflow buyers judge fast

Course creators, coaching businesses, and LMS teams usually know that progress-based email works better than a fixed drip. The hard part is delivering that signal into the email system consistently.

A student who just finished a lesson needs a different follow-up from a student who registered three days ago and has not started. Behavioral timing keeps the message aligned with the learner state.

Once you have several module paths, milestone reminders, and re-engagement branches, hand-built audience sync scripts become one more brittle system to debug whenever a learner misses the right sequence.

What it depends on

The supporting pieces behind a credible rollout

These pages stay focused on the workflow outcome, but the setup still needs the right workspace, destination connection, and event path underneath.

Meshes workspace

You need a workspace and publishable key so your app can emit lesson.completed.

Mailchimp audience plan

Create the audiences or list states that should represent next lesson, module recap, milestone reminder, or completion follow-up.

Lesson completion event path

Your product should emit lesson.completed with the student and progress fields Mailchimp needs.

Rule and mapping docs

Use the connection and rule docs for the implementation details behind the Mailchimp handoff.

The source event

The payload that creates the downstream business outcome

For Mailchimp, the event needs enough context to place the learner into the right audience state and give the downstream email logic a useful view of what just happened.

Event payload

lesson.completed

{
  "student_id": "stu_2048",
  "email": "nina@academyflow.io",
  "lesson_id": "lesson_customer-research",
  "lesson_title": "Customer Research Fundamentals",
  "module_id": "module_growth-foundations",
  "course_id": "course_creator-accelerator",
  "completion_percentage": 62
}

What matters most

email
Mailchimp needs a stable contact identity so the student lands in the right audience entry.
lesson_title
Gives the next email path human-readable context about what the learner just completed.
module_id
Supports module-specific follow-up instead of one generic post-lesson sequence.
course_id
Keeps audience entry logic explicit when multiple programs share one workspace.
completion_percentage
Helps you reserve milestone sequences for the progress thresholds that matter most.

Field mapping view

What the destination needs from the event

Event field	Destination target	Why it matters
email	Mailchimp subscriber identity	Identifies which contact should be added to the audience or list state.
lesson_title	Merge field or internal context	Makes the resulting Mailchimp automation more specific than a generic course follow-up.
module_id	Rule selection or module-specific audience	Lets you split follow-up by module instead of funneling every student into one path.
course_id	Audience boundary	Keeps different course programs from sharing the same nurture path by mistake.
completion_percentage	Milestone audience logic	Supports milestone reminders or completion pushes when a threshold matters more than the exact lesson name.

The destination connection

The destination matters, but the connection quality matters just as much

In your Meshes workspace, connect Mailchimp and confirm the audiences or lists that represent the next lesson, recap, milestone reminder, or completion follow-up. Once that connection is available in Meshes, you can bind lesson.completed to the exact audience state your Mailchimp automation watches.

Create or connect the Mailchimp account inside the workspace that owns the course events.
Confirm which audiences or lists correspond to next lesson, recap, milestone, or completion follow-up.
Keep the audience naming explicit so the rule reads like business intent, not list admin trivia.
If multiple courses share the workspace, decide whether audience separation happens by course_id, connection, or resource context.

Integrations & Rules Meshes quickstart

Where Meshes matters

The product stays simple while the destination still gets the right shape

Most teams do not need another destination. They need the destination to stay in sync without embedding its delivery quirks, retries, and mapping logic into the product code path.

Event

lesson.completed

Destination

Mailchimp

Use case

Lesson Completion Flows

Docs

Integrations & Rules

In Meshes, create a Mailchimp add_to_list rule for each meaningful lesson-completion outcome. Meshes delivers the learner into the audience state selected in the rule, and Mailchimp handles the automation that starts once the student lands there.

Use separate audience states for meaningfully different follow-up paths such as next lesson, recap, reminder, or completion.
Keep lesson.completed as the only source event and let the routing structure decide which Mailchimp audience should receive it.
If multiple courses share the workspace, use course-specific resource or resource_id values where that keeps the rules easier to audit.
Let Mailchimp own the campaign or journey after Meshes completes the audience handoff.

A sample event

The product-side code stays close to the business event

This is the part teams like: the source event stays readable and product-shaped while Meshes owns the destination-facing complexity.

TypeScript example

One emit call stays close to the business event

import MeshesEventsClient from '@mesheshq/events';

const events = new MeshesEventsClient(process.env.WORKSPACE_PUBLISHABLE_KEY!);

await events.emit({
  event: 'lesson.completed',
  resource: 'course',
  resource_id: 'course_creator-accelerator',
  payload: {
    student_id: 'stu_2048',
    email: 'nina@academyflow.io',
    lesson_id: 'lesson_customer-research',
    lesson_title: 'Customer Research Fundamentals',
    module_id: 'module_growth-foundations',
    course_id: 'course_creator-accelerator',
    completion_percentage: 62,
  },
});

Destination outcome

Use Send Test Event in Meshes or emit a representative lesson.completed event from your product, then inspect Mailchimp. The learner should be added to the audience or list state that owns the next lesson, recap, reminder, or completion sequence for that milestone.

Send Events SDK docs

Operational visibility

Delivery history is where this stops feeling like glue code

The difference between a nice demo and a usable product workflow is whether you can see what happened when the destination is slow, misconfigured, or unavailable.

In Meshes

What a healthy workflow looks like

Confirm the lesson.completed event appears in Meshes and the Mailchimp rule is matched.
Check delivery history for a successful add_to_list attempt.
Open the Mailchimp audience and verify the learner landed in the intended list state.
If the audience update fails, use Meshes failure details and replay after fixing the list selection or credentials.

Why teams buy Meshes

The workflow stays sellable after launch

Retries keep a temporary Mailchimp issue from breaking the behavior-based email path.
Replay gives you a clean recovery path when an audience or connection issue is fixed after students have already progressed.
Delivery history makes it obvious whether the lesson signal reached Mailchimp or disappeared into sync glue code.

What's next

Keep exploring the same workflow from different angles

Use Case

Lesson Completion Flows

See the broader lesson.completed fan-out pattern across CRM, lifecycle email, Slack, and milestone automation.

Open link

Docs

Integrations & Rules

Review how Meshes connections, actions, and rule metadata shape the Mailchimp handoff.

Open link

Docs

Send Events

Use the Meshes event API or SDK to emit lesson.completed from your product.

Open link

Compare

Meshes vs. DIY

Compare progress-based Mailchimp routing with maintaining your own list-sync and retry logic.

Open link

Guide

Update HubSpot on Lesson Completion

Project the same lesson.completed signal into HubSpot progress fields and lifecycle lists.

Open link

Guide

Trigger ActiveCampaign Onboarding Sequences from Page Completion

See another guide where the next lifecycle message starts from actual progress instead of generic timing.

Open link

Next stepStart free or keep reading the docs

Start the next Mailchimp sequence from the lesson the learner just finished

Emit `lesson.completed` once, let Meshes handle the audience handoff, and keep your course emails aligned with real student progress.

Start free View documentation

WorkflowCourse progress workflow

Send Lesson Completion Events to Mailchimp Sequences

Use Meshes to route `lesson.completed` into the Mailchimp audience or list state that should own the next email, whether that means the next lesson, a module recap, a milestone reminder, or a completion push.

Start free View documentation

Event signal:lesson.completed| Destination:Mailchimp| Use case:Lesson Completion Flows| Typical setup:~15 minutes

Workflow outcome

The product event is small. The downstream effect is not.

The workflow begins with one lesson.completed event from your course product and ends with the learner inside the Mailchimp audience state that should trigger the next relevant sequence.

That replaces generic drip timing with behavior-based timing. Instead of hoping the student is ready when the next email is scheduled, the email path starts because the lesson was actually completed.

Why teams care

This is the kind of workflow buyers judge fast

Course creators, coaching businesses, and LMS teams usually know that progress-based email works better than a fixed drip. The hard part is delivering that signal into the email system consistently.

A student who just finished a lesson needs a different follow-up from a student who registered three days ago and has not started. Behavioral timing keeps the message aligned with the learner state.

What it depends on

The supporting pieces behind a credible rollout

These pages stay focused on the workflow outcome, but the setup still needs the right workspace, destination connection, and event path underneath.

Meshes workspace

You need a workspace and publishable key so your app can emit lesson.completed.

Mailchimp audience plan

Create the audiences or list states that should represent next lesson, module recap, milestone reminder, or completion follow-up.

Lesson completion event path

Your product should emit lesson.completed with the student and progress fields Mailchimp needs.

Rule and mapping docs

Use the connection and rule docs for the implementation details behind the Mailchimp handoff.

The source event

The payload that creates the downstream business outcome

For Mailchimp, the event needs enough context to place the learner into the right audience state and give the downstream email logic a useful view of what just happened.

Event payload

lesson.completed

{
  "student_id": "stu_2048",
  "email": "nina@academyflow.io",
  "lesson_id": "lesson_customer-research",
  "lesson_title": "Customer Research Fundamentals",
  "module_id": "module_growth-foundations",
  "course_id": "course_creator-accelerator",
  "completion_percentage": 62
}

What matters most

email
Mailchimp needs a stable contact identity so the student lands in the right audience entry.
lesson_title
Gives the next email path human-readable context about what the learner just completed.
module_id
Supports module-specific follow-up instead of one generic post-lesson sequence.
course_id
Keeps audience entry logic explicit when multiple programs share one workspace.
completion_percentage
Helps you reserve milestone sequences for the progress thresholds that matter most.

Field mapping view

What the destination needs from the event

Event field	Destination target	Why it matters
email	Mailchimp subscriber identity	Identifies which contact should be added to the audience or list state.
lesson_title	Merge field or internal context	Makes the resulting Mailchimp automation more specific than a generic course follow-up.
module_id	Rule selection or module-specific audience	Lets you split follow-up by module instead of funneling every student into one path.
course_id	Audience boundary	Keeps different course programs from sharing the same nurture path by mistake.
completion_percentage	Milestone audience logic	Supports milestone reminders or completion pushes when a threshold matters more than the exact lesson name.

The destination connection

The destination matters, but the connection quality matters just as much

Create or connect the Mailchimp account inside the workspace that owns the course events.
Confirm which audiences or lists correspond to next lesson, recap, milestone, or completion follow-up.
Keep the audience naming explicit so the rule reads like business intent, not list admin trivia.
If multiple courses share the workspace, decide whether audience separation happens by course_id, connection, or resource context.

Integrations & Rules Meshes quickstart

Where Meshes matters

The product stays simple while the destination still gets the right shape

Most teams do not need another destination. They need the destination to stay in sync without embedding its delivery quirks, retries, and mapping logic into the product code path.

Event

lesson.completed

Destination

Mailchimp

Use case

Lesson Completion Flows

Docs

Integrations & Rules

Use separate audience states for meaningfully different follow-up paths such as next lesson, recap, reminder, or completion.
Keep lesson.completed as the only source event and let the routing structure decide which Mailchimp audience should receive it.
If multiple courses share the workspace, use course-specific resource or resource_id values where that keeps the rules easier to audit.
Let Mailchimp own the campaign or journey after Meshes completes the audience handoff.

A sample event

The product-side code stays close to the business event

This is the part teams like: the source event stays readable and product-shaped while Meshes owns the destination-facing complexity.

TypeScript example

One emit call stays close to the business event

import MeshesEventsClient from '@mesheshq/events';

const events = new MeshesEventsClient(process.env.WORKSPACE_PUBLISHABLE_KEY!);

await events.emit({
  event: 'lesson.completed',
  resource: 'course',
  resource_id: 'course_creator-accelerator',
  payload: {
    student_id: 'stu_2048',
    email: 'nina@academyflow.io',
    lesson_id: 'lesson_customer-research',
    lesson_title: 'Customer Research Fundamentals',
    module_id: 'module_growth-foundations',
    course_id: 'course_creator-accelerator',
    completion_percentage: 62,
  },
});

Destination outcome

Send Events SDK docs

Operational visibility

Delivery history is where this stops feeling like glue code

The difference between a nice demo and a usable product workflow is whether you can see what happened when the destination is slow, misconfigured, or unavailable.

In Meshes

What a healthy workflow looks like

Confirm the lesson.completed event appears in Meshes and the Mailchimp rule is matched.
Check delivery history for a successful add_to_list attempt.
Open the Mailchimp audience and verify the learner landed in the intended list state.
If the audience update fails, use Meshes failure details and replay after fixing the list selection or credentials.

Why teams buy Meshes

The workflow stays sellable after launch

Retries keep a temporary Mailchimp issue from breaking the behavior-based email path.
Replay gives you a clean recovery path when an audience or connection issue is fixed after students have already progressed.
Delivery history makes it obvious whether the lesson signal reached Mailchimp or disappeared into sync glue code.

What's next

Keep exploring the same workflow from different angles

Use Case

Lesson Completion Flows

See the broader lesson.completed fan-out pattern across CRM, lifecycle email, Slack, and milestone automation.

Open link

Docs

Integrations & Rules

Review how Meshes connections, actions, and rule metadata shape the Mailchimp handoff.

Open link

Docs

Send Events

Use the Meshes event API or SDK to emit lesson.completed from your product.

Open link

Compare

Meshes vs. DIY

Compare progress-based Mailchimp routing with maintaining your own list-sync and retry logic.

Open link

Guide

Update HubSpot on Lesson Completion

Project the same lesson.completed signal into HubSpot progress fields and lifecycle lists.

Open link

Guide

Trigger ActiveCampaign Onboarding Sequences from Page Completion

See another guide where the next lifecycle message starts from actual progress instead of generic timing.

Open link

Next stepStart free or keep reading the docs

Start the next Mailchimp sequence from the lesson the learner just finished

Emit `lesson.completed` once, let Meshes handle the audience handoff, and keep your course emails aligned with real student progress.

Start free View documentation

WorkflowCourse progress workflow

Send Lesson Completion Events to Mailchimp Sequences

Use Meshes to route lesson.completed into the Mailchimp audience or list state that should own the next email, whether that means the next lesson, a module recap, a milestone reminder, or a completion push.

The product event is small. The downstream effect is not.

This is the kind of workflow buyers judge fast

The supporting pieces behind a credible rollout

Meshes workspace

Mailchimp audience plan

Lesson completion event path

Rule and mapping docs

The payload that creates the downstream business outcome

What the destination needs from the event

The destination matters, but the connection quality matters just as much

The product stays simple while the destination still gets the right shape

The product-side code stays close to the business event

One emit call stays close to the business event

Delivery history is where this stops feeling like glue code

What a healthy workflow looks like

The workflow stays sellable after launch

Keep exploring the same workflow from different angles

Lesson Completion Flows

Integrations & Rules

Send Events

Meshes vs. DIY

Update HubSpot on Lesson Completion

Trigger ActiveCampaign Onboarding Sequences from Page Completion

Next stepStart free or keep reading the docs

Start the next Mailchimp sequence from the lesson the learner just finished

Emit lesson.completed once, let Meshes handle the audience handoff, and keep your course emails aligned with real student progress.

WorkflowCourse progress workflow

Send Lesson Completion Events to Mailchimp Sequences

Use Meshes to route lesson.completed into the Mailchimp audience or list state that should own the next email, whether that means the next lesson, a module recap, a milestone reminder, or a completion push.

The product event is small. The downstream effect is not.

This is the kind of workflow buyers judge fast

The supporting pieces behind a credible rollout

Meshes workspace

Mailchimp audience plan

Lesson completion event path

Rule and mapping docs

The payload that creates the downstream business outcome

What the destination needs from the event

The destination matters, but the connection quality matters just as much

The product stays simple while the destination still gets the right shape

The product-side code stays close to the business event

One emit call stays close to the business event

Delivery history is where this stops feeling like glue code

What a healthy workflow looks like

The workflow stays sellable after launch

Keep exploring the same workflow from different angles

Lesson Completion Flows

Integrations & Rules

Send Events

Meshes vs. DIY

Update HubSpot on Lesson Completion

Trigger ActiveCampaign Onboarding Sequences from Page Completion

Next stepStart free or keep reading the docs

Start the next Mailchimp sequence from the lesson the learner just finished

Emit lesson.completed once, let Meshes handle the audience handoff, and keep your course emails aligned with real student progress.

Use Meshes to route `lesson.completed` into the Mailchimp audience or list state that should own the next email, whether that means the next lesson, a module recap, a milestone reminder, or a completion push.

Emit `lesson.completed` once, let Meshes handle the audience handoff, and keep your course emails aligned with real student progress.

Use Meshes to route `lesson.completed` into the Mailchimp audience or list state that should own the next email, whether that means the next lesson, a module recap, a milestone reminder, or a completion push.

Emit `lesson.completed` once, let Meshes handle the audience handoff, and keep your course emails aligned with real student progress.