FluentCRM already knows who your contacts are and what they signed up for. FlowMattic adds WhatsApp as a second channel, sending template, text, image or document messages through the WhatsApp Cloud API when a contact is created, tagged, added to a list or has an email bounce. It all runs from the WordPress site FluentCRM lives on.
20 triggers 56 actions 6 example workflows 2 ready-made templates Unlimited runs
When this happens in FluentCRM20 triggers
Do this in WhatsApp Cloud API5 actions
1. TriggerNew Contact Created2. ActionSend Template MessageWhen FluentCRM fires New Contact Created, FlowMattic runs Send Template Message in WhatsApp Cloud API 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 templateA Router checks the new contact's status. Subscribed contacts get your welcome template, and pending ones get a reminder to confirm their email.
New Contact CreatedRouterSend Template Message
View the template When a contact gets your webinar tag, they receive a template with the date and link, and a Delay sends a second template shortly before the start.
Contact Added to TagsSend Template MessageDelaySend Template Message
A bounce means the email address is wrong. A template asks the contact to update it, and a tag in FluentCRM marks who has been asked.
Email BouncedSend Template MessageAdd Tags to Contact
A Filter passes only clicks on your pricing or booking link and sends the rep a WhatsApp template with the contact's name and email, so they can follow up while interest is fresh.
Email ClickedFilterSend Template Message
When the purchase tag is added, the contact gets the guide as a WhatsApp document, which is easier to find again on a phone than an email attachment.
Contact Added to TagsFilterSend Document Message
Adding a contact to the VIP list sends them the offer as an image message and logs it as an event on their FluentCRM profile.
Contact Added to ListsSend Image MessageAdd Event to Contact
At the end, each new FluentCRM contact with a phone number gets the WhatsApp message that fits their status.
In your WhatsApp Business account, create the welcome and confirm-your-email templates and wait until they are approved.
In FlowMattic, add the WhatsApp Cloud API connection under Connects. FluentCRM runs on the same site, so it needs no connection.
Start a workflow with FluentCRM's New Contact Created and add a test contact with a phone number in international format.
Add a Router with one path for subscribed and one for pending, each with its own Send Template Message.
Map the phone number and first name into each template, test both paths on your own number and switch the workflow on.
1. Trigger in FluentCRM
New Contact Created
3. Action in WhatsApp Cloud API
Send Template Message
Fields mapped from the earlier steps (a typical setup)
| From FluentCRM | To WhatsApp Cloud API |
|---|---|
| Phone | Recipient number |
| First name | Template name variable |
| Status | Router condition |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
FluentCRM and WhatsApp Cloud API connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
FluentCRM, FlowMattic and the trigger data all live on your WordPress site, so no contact list has to be exported.
Runs are unlimited on every plan, so messaging every new contact adds nothing to your FlowMattic plan.
Actions like Add Tags to Contact and Add Event to Contact let the same workflow note on the profile which WhatsApp message went out.
Yes, as a workflow. Use a Schedule with Get Contact by List IDs, loop over the contacts with Iterator and send a template to each. Only message contacts who agreed to hear from you on WhatsApp.
From the contact's phone field in FluentCRM, or a custom field if you store it there. Keep numbers in international format so the message reaches the right country.
Not with the workflows on this page, which start from FluentCRM events. Workflows run from FluentCRM to WhatsApp.
Yes. Add a Filter on the contact's status before the WhatsApp step, or start a workflow from Contact Status Change to Unsubscribed that adds a tag your other workflows check.
Did not find your answer? You can browse the help center or ask us directly.
FluentCRM and Slack35 shared templates
FluentCRM and Fluent Forms30 shared templates
FluentCRM and AI Agents24 shared templates
FluentCRM and Google Sheets19 shared templates
FluentCRM and WooCommerce10 shared templates
FluentCRM and Mailchimp7 shared templates
FluentCRM and WordPress7 shared templates
FluentCRM and Facebook Lead Ads5 shared templatesWhatsApp Cloud API and WooCommerce13 shared templates
WhatsApp Cloud API and Fluent Forms6 shared templates
WhatsApp Cloud API and Contact Form 75 shared templates
WhatsApp Cloud API and Facebook Lead Ads4 shared templates
WhatsApp Cloud API and Google Sheets3 shared templates
WhatsApp Cloud API and Fluent Support3 shared templates
WhatsApp Cloud API and Telegram3 shared templates
WhatsApp Cloud API and Typeform2 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. FluentCRM integration 2.1.1, WhatsApp Cloud API integration 1.0.1.