Send Every Lead Into FluentCRM
DM Champ connects to FluentCRM on your own WordPress site so a new WhatsApp lead becomes a contact with the right tag on it, and the email sequence you already built takes over. You paste your site address, your WordPress username and an application password. Nothing is installed on your site.
How it worksConnecting FluentCRM Step by Step
What the setup actually looks like, from the connection screen to the first booking or record the AI handles in FluentCRM.
- 01Create an application password in WordPress
FluentCRM rides on the WordPress REST API, so it takes the same credentials WordPress itself does. In WordPress go to Users, then Profile, then Application Passwords, and click Add New. Copy it with its spaces. That user needs to be allowed to manage FluentCRM.
- 02Add a FluentCRM step to an automation
Open Automations in the sidebar under AI Studio, add a step and search for FluentCRM. Pick the action you want and the step asks you to connect first.
- 03Paste your site address and credentials
Site URL is the WordPress site FluentCRM runs on, starting with https, plus the WordPress username and the application password. We read one contact back out of FluentCRM before anything saves, so wrong details are refused on screen with the reason.
- 04Note down your tag and list ids
Every tag and list field wants id numbers, comma separated, not names. Open Tags or Lists in the FluentCRM menu and each row's id is in the address bar when you open it. Write down the handful you plan to use once.
- 05Wire the steps together
Find contact by email turns an email address into the contact id that the tag and list steps need, and every field takes data from earlier steps with the usual insert-data buttons.
Every screen and field is covered in the setup guide: FluentCRM documentation.
The stepsFive Actions For Contacts, Tags and Lists
Create or update contact is the one you will use most: sending the same email twice updates that person rather than failing, so you can run it on every new lead without checking first. The rest work on a contact id, which is what Find contact by email is for.
- Create or update contact: email, optional first name, last name and phone, a status of subscribed, pending, unsubscribed or bounced, plus optional tag ids and list ids
- Find contact by email: returns their id, their tags and their lists
- Add tags to contact: contact id, the contact's email, and the tag ids to attach
- Remove tags from contact: the same fields, taking tags off instead
- Add contact to lists: contact id, the contact's email, and the list ids
Read this firstTags and Lists Are Given As ID Numbers
This is the one thing to know before you build anything. Every field that takes tags or lists wants their id numbers, comma separated, not their names. The numbers live in FluentCRM: open Tags or Lists in the FluentCRM menu and each row's id is in the address bar when you open it. A name typed into that field simply will not match, so note down the handful you plan to use and you are done. FluentCRM also asks for the contact's email on every update, which is why the tag and list steps take both the contact id and the email.
The workflow to copyWhatsApp Handles the Chat, Email Handles the Nurture
The version worth building is the one where the tag comes from the conversation rather than from the first message, because that is the tag your email sequence should react to. Nobody moves a row between two systems by hand again.
- Your AI agent adds a tag such as asked about pricing to the contact during the conversation
- Find contact by email turns the contact's email into their FluentCRM id
- Add tags to contact attaches the FluentCRM tag id that starts your pricing sequence
- FluentCRM's own automation sends the emails from there, exactly as it already does
- The simpler version, for every new lead: Create or update contact with their email, name and phone plus your main list id, straight off an incoming message
Worth knowingThe Limits, Stated Up Front
These change how you wire the automation rather than what it can do. The direction of travel is the important one: these steps write into FluentCRM, they do not watch it.
- There is no polling trigger, so nothing watches FluentCRM for changes
- To have FluentCRM start an automation, point a FluentCRM outgoing webhook at the address the automation's Webhook trigger gives you
- The site needs https and pretty permalinks switched on, anything other than Plain, or the API address does not resolve
- Some hosts strip the Authorization header before WordPress sees it, which makes a correct application password look wrong
- Your application password is stored encrypted and never shown back to you
- Anything not among the five actions is still possible with the HTTP request step
Frequently Asked.
Meet the Closer. Then Decide.
The same AI agent that closes $40K deals in DMs is one click away. No signup, no demo call - open the chat, push back, see if you can break it.
