Create Breeze cards from MailerLite subscriber updates for onboarding workflows
Whenever a MailerLite subscriber’s custom fields change, FlowMattic creates a card in Breeze, so your team gets a task to act on that subscriber’s new details.
MailerLite
Breeze2 steps Setup ~5 min Used on 1.9k sites Productivity Free to import
What this workflow does
Custom fields in MailerLite often carry the signals that matter for onboarding: a plan name, a company size, a stage someone has reached. When one of those changes, someone on your team may need to do something. This workflow puts that change on your Breeze board as a card, instead of leaving it buried in the email tool.
The MailerLite Subscriber Updated trigger fires when any of a subscriber's custom fields are updated. It doesn't care which field changed, so every custom-field edit starts its own run.
The Breeze step then creates a new card. It ships unmapped: after import you connect Breeze, set where the card should go on your board, and map the subscriber's email, name and the updated fields into the card's title and description.
Because the step always creates a fresh card, a subscriber whose fields change three times produces three cards. If only one field should open a task, add a Filter on it, as described in the tips. Update a test subscriber in MailerLite and check Task History to see which fields the trigger delivers.
Onboarding call after a plan field changes
A SaaS team stores each subscriber's plan in a MailerLite custom field. When it changes to a paid plan, a Breeze card reminds the success manager to book a welcome call.
Account setup tasks for an agency
An agency's intake form fills MailerLite custom fields such as website URL and budget, and each update puts a card on the onboarding board for the project lead.
Follow-up when a subscriber changes company
A B2B newsletter tracks company name in a custom field, and sales gets a Breeze card to review the contact whenever that value is edited.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
MailerLite Subscriber UpdatedFires when any custom field on a MailerLite subscriber is updated. The subscriber's email and field values are passed to the Breeze step, whichever field changed.
- Breeze Create Card
Creates a card in Breeze. The template leaves it unmapped, so after import set where the card lands, then map the subscriber's details and updated fields into the card.
What you need
- FlowMatticCore
- MailerLite AccountAccount
- Breeze 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 MailerLite trigger and the Breeze step that continues only when your onboarding field holds the value you care about, such as a plan name. The field and value in that Filter are examples to change for your account.
- Put the subscriber's email in the card title, so cards for the same person are easy to spot on the board.
- Give each card an onboarding checklist by adding Breeze's Create Todo List action after the Create Card step and mapping the card that step 2 returns.
Questions about this workflow
Does every MailerLite custom field change create a Breeze card?
Yes, as imported. The trigger fires for updates to any custom field. Add a Filter between the MailerLite trigger and the Breeze step to create cards only for the field and value that mean onboarding work.
Will new MailerLite subscribers create cards?
Not through this trigger, which reacts to custom-field updates. FlowMattic's MailerLite integration has a separate Subscriber Created trigger if new sign-ups should get a card too.
Where in Breeze do the cards appear?
Wherever you point the Create Card step after import. Run a test update and check the board, then adjust the step until cards land in the column your team works from.
Can the workflow update an existing card instead of making a new one?
Not as shipped. Create Card always adds a new card. Breeze's Update Card action needs the ID of the card to change, and nothing in this flow stores it.
More Project Management workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted