WordPress and Brevo (Sendinblue) workflows you can build
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made template Add each new WordPress user as a Brevo contact
Everyone who registers on your site is in Brevo with their email and name, ready for your welcome series and newsletters without a weekly CSV export.
New User→Create a New Contact
View the templateUpdate the Brevo contact when a user edits their profile
A changed name or other profile detail is sent with Update a Contact, so the greeting in your next campaign uses what the member typed last.
User Profile Updated→Update a Contact
Remove the Brevo contact when a WordPress account is deleted
When you delete a user on request, Delete a Contact removes them from Brevo in the same run, so a privacy request does not leave a copy behind in your email tool.
User Deleted→Delete a Contact
Store each member's role as a Brevo attribute
When a user's role changes, for example from subscriber to customer, Update a Contact writes the new role to an attribute your Brevo segments use, so paying members get member emails.
User Role Changed→Update a Contact
Mark unsubscribed contacts on their WordPress user
Brevo's Message Unsubscribed finds the user by email and saves an opt-out flag in user meta, so other plugins and forms on your site can respect the choice too.
Message Unsubscribed→Get User by Email→Update User Meta
Flag users whose email hard bounced
A hard bounce means the address does not work. Saving that on the user lets you ask them to fix their email the next time they log in.
Message Hard Bounced→Get User by Email→Update User Meta
Give a beta role to members who click the join link
Send a campaign with a join-the-beta link. A Filter picks clicks on that link and Add Role to User gives those members the beta role on your site.
Message Clicked→Filter→Get User by Email→Add Role to User