Create or update MailerLite subscribers for new Heartbeat users

When a new user joins your Heartbeat community, this workflow creates them as a MailerLite subscriber, or updates their record if the address is already on your list, so community members can receive your emails.

Heartbeat

MailerLite

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 2.8k sites Free to import

The Create or update MailerLite subscribers for new Heartbeat users workflow on the FlowMattic canvas, with 2 steps across Heartbeat, MailerLite — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

A Heartbeat community is where members talk, but newsletters, event reminders and course announcements often go out by email. If new members only exist in Heartbeat, someone has to export them and import them into MailerLite before they get any of that. This workflow adds each new member to MailerLite when they join.

The Heartbeat trigger runs when a new user joins your community and sends their details to FlowMattic. The MailerLite step uses Create or Update Subscriber, so a new email address becomes a new subscriber and an address that is already on your list has its record updated rather than duplicated.

Each new member produces one run. The workflow does not remove anyone from MailerLite when they leave Heartbeat. Invite a test member after import and check Task History to see which details Heartbeat provides, then map the email and name into the subscriber.

Welcome emails for a paid community

New Heartbeat members become MailerLite subscribers, so they receive the welcome sequence you already run from MailerLite.

Course cohorts run in Heartbeat

Students join the cohort community in Heartbeat and are added to MailerLite, where you send lesson reminders and live session links.

Keeping a list of everyone who joined

Members who sign up for the community are added to your MailerLite audience, so your list includes people who joined through Heartbeat, not just your site.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Heartbeat New User
Runs when a new user joins your Heartbeat community. Their member details are passed on for mapping into the MailerLite subscriber.
Step 2Action
MailerLite Create or Update Subscriber
Adds the member to MailerLite as a subscriber, or updates the subscriber if that email is already there. Connect your MailerLite account and map the Heartbeat email and name into it.

What you need

FlowMatticCore
Heartbeat AccountAccount
MailerLite AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Check the MailerLite step after import for group options. Putting Heartbeat members in their own group lets you email them separately from other subscribers.
Add a Slack or Gmail step after MailerLite so a community manager hears about each new member as well.
Invite yourself as a test member after import, then look at the run in Task History to confirm the email field before you switch the workflow on.

Questions about this workflow

What happens if the Heartbeat member is already a MailerLite subscriber?

The action is Create or Update Subscriber, so their existing MailerLite record is updated with the details you map instead of a second subscriber being added.

Does leaving the Heartbeat community unsubscribe someone from MailerLite?

No. The workflow only reacts to new users joining. Removals in Heartbeat do not change MailerLite.

Are existing Heartbeat members added when I import this?

No. Only users who join after the workflow is turned on are sent to MailerLite. Import earlier members from a Heartbeat export if you need them.

Do new members need to agree to emails before being added to MailerLite?

That depends on your own consent rules and region. The workflow adds every new member it receives, so make sure your Heartbeat sign-up tells members they will get emails.