When a Snackeet story is completed or abandoned, add the viewer to MailerLite

When a viewer finishes or leaves a Snackeet story, FlowMattic adds them to MailerLite as a new subscriber or updates the subscriber they already are, ready for your email follow-up.

Snackeet

MailerLite

Download this workflow Browse more workflows

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

The When a Snackeet story is completed or abandoned, add the viewer to MailerLite workflow on the FlowMattic canvas, with 2 steps across Snackeet, MailerLite — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Interactive stories and quizzes in Snackeet collect details from people who are curious about you, but those answers stay in Snackeet unless you move them. This workflow sends each viewer who reaches the end of a story, or drops out partway, into MailerLite, so the emails you already run there can follow up.

The Snackeet trigger starts a run when a story is completed or abandoned, and passes on the data Snackeet recorded for that viewer. The MailerLite step then creates a subscriber, or updates the existing one with the same email, including any custom fields you map.

The MailerLite step ships unmapped. After import, map the viewer's email and any answers you want to keep, such as a quiz result or chosen product, into subscriber fields. A subscriber needs an email address, so your story should ask for one; viewers who leave before giving it reach the workflow without it.

Completed and abandoned stories both run the same step. If you treat the two groups differently, record which one it was in a custom field or split them with a Router between the Snackeet trigger and the MailerLite step. Check Task History after a test run to see what Snackeet sent.

Product quiz leads for a skincare shop

A shop's Snackeet skin-type quiz adds each finisher to MailerLite with their result in a custom field, so the brand can send routine suggestions that match.

Win back viewers who stopped early

A course creator follows up with people who left a Snackeet story after entering their email, inviting them to finish it or book a call.

Event teaser stories

An event organiser runs a Snackeet story about an upcoming conference and keeps everyone who opts in on MailerLite for ticket announcements.

How this workflow runs

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

Step 1Trigger
Snackeet Configure Webhook
Fires when a viewer completes or abandons one of your Snackeet stories. Both outcomes start a run, and the details the viewer entered are handed to the MailerLite step.
Step 2Action
MailerLite Create or Update Subscriber
Creates a new MailerLite subscriber, or updates an existing one, with the custom fields you map. The template leaves its fields blank, so connect MailerLite and map at least the viewer's email address.

What you need

FlowMatticCore
Snackeet 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.

Put a Filter between the Snackeet trigger and the MailerLite step that continues only when the email is not empty, so viewers who left before typing it don't reach MailerLite.
To handle completers and dropouts apart, put a Router between the Snackeet trigger and the MailerLite step, move that step into one route, give the other route its own copy, and use outcome conditions that can't both match.
Add MailerLite's Add Subscriber to a Group action after the subscriber step and map the subscriber it created, so your MailerLite automations can start from that group.

Questions about this workflow

Does a viewer who abandons a Snackeet story still reach MailerLite?

Yes, abandoned stories start a run too. MailerLite can only add them if the viewer typed an email before leaving, so check a test run for what Snackeet sent at that point.

Can I tell completed and abandoned Snackeet viewers apart in MailerLite?

Look at a test run of each kind in Task History to find the value that marks the outcome, then map it into a MailerLite custom field, or test it in a Router placed between the Snackeet trigger and the MailerLite step.

What if the viewer is already a MailerLite subscriber?

The step creates or updates, so MailerLite updates the existing subscriber with the fields you mapped instead of adding a duplicate.