Keep your Campaign Monitor lists in step with the people who register on your WordPress site. New users become subscribers, profile edits update them, an opt-out field unsubscribes them and erased accounts leave the list. FlowMattic runs it on the same WordPress site, so user data goes from your database straight to Campaign Monitor.
32 triggers 75 actions 7 example workflows 2 ready-made templates Unlimited runs
When this happens in WordPress32 triggers
Do this in Campaign Monitor4 actions
1. TriggerNew User2. ActionAdd SubscriberWhen WordPress fires New User, FlowMattic runs Add Subscriber in Campaign Monitor with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
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 templateMembership sites, course sites and shops with accounts get every new registration on the list they email, so the welcome campaign reaches people who just joined.
New UserAdd Subscriber
View the template Personalised emails go wrong when a user fixes their name on the site but the list keeps the old one. Update Subscriber copies the new details across.
User Profile UpdatedUpdate Subscriber
When the profile field that holds newsletter consent changes, a Router reads the new value. Unticked users are unsubscribed and ticked users are added back.
User Profile Field UpdatedRouterUnsubscribe
Paid members, students or wholesale buyers often get emails nobody else should see. When a role is added, a Router adds the user to the list for that role.
User Role AddedRouterAdd Subscriber
When an account is deleted in wp-admin, the matching subscriber is deleted from the list too, so you stop emailing people who left the site.
User DeletedDelete Subscriber
WordPress handles erasure requests for its own data. This workflow carries the confirmed request to Campaign Monitor as well, so the email list is part of the same clean-up.
GDPR Erase Data Request ConfirmedDelete Subscriber
Get All Users by Role lists the accounts you already have. Iterator walks the list and adds each one, so the list starts complete. Run it once, then rely on New User.
ScheduleGet All Users by RoleIteratorAdd Subscriber
At the end, every new WordPress registration is added as a subscriber to the Campaign Monitor list you choose.
Under Connects, add Campaign Monitor with the API key from your Campaign Monitor account settings.
Create a workflow with the WordPress New User trigger. WordPress needs no connection. Register a test user so FlowMattic captures the user's fields.
Add Campaign Monitor Add Subscriber, choose the list, and map the user's email and display name.
Test the step, check the subscriber appears on the list in Campaign Monitor, then switch the workflow on.
1. Trigger in WordPress
New User
2. Action in Campaign Monitor
Add Subscriber
Fields mapped from the earlier steps (a typical setup)
| From WordPress | To Campaign Monitor |
|---|---|
| User email | Email address |
| Display name | Name |
| Role | Custom field |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
WordPress and Campaign Monitor connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Registrations, profile edits, roles and deletions all reach Campaign Monitor, so the list matches the people actually on your site.
Erasure requests confirmed in WordPress also remove the subscriber, which saves a manual step every time someone asks.
FlowMattic runs on your WordPress site with unlimited runs, so subscribers move from your database to Campaign Monitor with no service in between.
Create a workflow with the WordPress New User trigger and a Campaign Monitor Add Subscriber step. Pick the list, map the email and name, test with one new user and switch it on.
Yes. Put a Router after New User or User Role Added with one path per role, and point each path's Add Subscriber step at its own list.
Campaign Monitor keeps them as unsubscribed, and your WordPress site is not told, because Campaign Monitor has no triggers here. Avoid re-adding them from WordPress events unless they opt in again on your site.
Yes. Trigger on User Role Changed, then use Delete Subscriber or Unsubscribe on the old list and Add Subscriber on the new one, with a Router deciding which lists apply.
No. New User runs for registrations after the workflow is live. To add earlier accounts, run a one-off workflow with Get All Users by Role, Iterator and Add Subscriber.
Did not find your answer? You can browse the help center or ask us directly.
WordPress and Slack17 shared templates
WordPress and Contact Form 715 shared templates
WordPress and LearnDash13 shared templates
WordPress and Brevo (Sendinblue)13 shared templates
WordPress and OpenAI (ChatGPT)11 shared templates
WordPress and Google Sheets10 shared templates
WordPress and Tutor LMS8 shared templates
WordPress and FluentCRM7 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. WordPress integration 7.3.0, Campaign Monitor integration 1.0.
