Add an engaged Netcore Cloud contact to a MailerLite group

When Netcore Cloud reports the engagement event you subscribe its webhook to, FlowMattic creates or updates that contact in MailerLite and adds them to a MailerLite group.

Netcore Cloud

MailerLite

Download this workflow Browse more workflows

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

The Add an engaged Netcore Cloud contact to a MailerLite group workflow on the FlowMattic canvas, with 3 steps across Netcore Cloud, MailerLite — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

People who open or click your Netcore Cloud emails have shown interest, and you may want to follow up with them from MailerLite. This workflow takes the contact from each Netcore event and places them in a MailerLite group you keep for engaged readers.

The Netcore Cloud trigger is a webhook receiver. FlowMattic describes it as firing when Netcore sends a response for a specified event, so you decide what counts as engagement: in Netcore's webhook settings, point the webhook at the FlowMattic URL and send only the event you want, for example clicks.

Next, MailerLite creates the subscriber, or updates them if the address is already in your account. The last step adds that subscriber to a MailerLite group. Both MailerLite steps ship unmapped: after import you map the email from the Netcore payload into the first step, and map the subscriber and choose the group in the second.

Every event Netcore sends starts a run, so a contact who clicks three times is processed three times. That is harmless for the group, but keep the webhook to the events you mean. Send a test event and check Task History to see the fields Netcore delivered.

Hot-lead group for clickers

A software company sends product news through Netcore Cloud and moves everyone who clicks a link into a MailerLite group that receives a demo invitation series.

Re-engagement audience

A publisher tracks opens in Netcore and keeps a MailerLite group of active readers, so its weekly digest in MailerLite goes to people who still read.

Splitting transactional and marketing email

A shop sends order emails through Netcore and uses MailerLite for newsletters; customers who click a link in an order email join a MailerLite group for offers.

How this workflow runs

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

Step 1Trigger
Netcore Cloud Setup Webhooks
Receives the webhook Netcore Cloud sends for the event you choose. Set the webhook in Netcore to only the engagement event you want, such as clicks, so other events don't start runs.
Step 2Action
MailerLite Create or Update Subscriber
Adds the contact to MailerLite as a new subscriber, or refreshes the existing record when that email is already there. The step ships unmapped: map the email and any name or custom fields from the Netcore payload.
Step 3Action
MailerLite Add Subscriber to a Group
Adds the subscriber from the previous step to a MailerLite group. After import, map that subscriber and choose the group you keep for engaged contacts.

What you need

FlowMatticCore
Netcore Cloud 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.

Send one test event from Netcore before mapping, so the payload's field names show up in FlowMattic and you can pick the recipient's email from them.
If Netcore sends several event types to this URL, put a Filter between the Netcore trigger and the Create or Update Subscriber step that continues only for the event name you want. Pick the field from a test payload.
Use a separate MailerLite group for each engagement level, for example clicked versus opened, and set up a second copy of this workflow with its own Netcore webhook for the other event.

Questions about this workflow

Which Netcore Cloud events will reach this MailerLite workflow?

Only the ones you send to the webhook URL. The trigger receives whatever Netcore posts, so choose the engagement event in Netcore's webhook settings and leave the rest off.

What if the contact is already a MailerLite subscriber?

The Create or Update Subscriber step updates the existing subscriber instead of creating a second one, then the next step adds them to the group.

Why does MailerLite need two steps here?

FlowMattic's Add Subscriber to a Group action works on a subscriber that already exists. The first step makes sure the person is in MailerLite before the group step runs.

Does a contact who clicks several times get added again?

Each event starts a new run, so both MailerLite steps run again for that person. The subscriber record is updated rather than duplicated. Open the repeat run in Task History to see what the group step returned.