CRM & email integration
FluentCRM AI agent tool reference
FluentCRM keeps contacts, their list and tag memberships, custom fields, campaigns and automations in its own tables. WP MCP Pro reads all of it (a setup summary, contacts filtered by list, tag and status, one contact with its lists, tags and field values, lists, tags, custom field definitions, campaigns and automations) and runs every write through FluentCRM's own API, so its hooks, automations and opt-in rules fire. Consent is never overridden: a new contact is created pending and sent FluentCRM's double opt-in email unless the site allows direct subscribes, an email that already belongs to a contact is refused rather than merged, the only status a write may set is unsubscribed, and a contact who unsubscribed, bounced or complained is refused from any list it would join. It tags and untags contacts, adds and removes them from lists, creates, renames and deletes lists and tags, bulk-imports contacts, and creates, updates, duplicates, tests and sends draft campaigns. Every write is snapshotted as a CRM rows image, so rollback is exact, except that mail cannot be unsent: a send or test is snapshotted but its undo is refused. Sending is off until a site enables it, and an unconfirmed send answers with the recipient count through the confirmation path first.
FluentCRM in plain language: FluentCRM MCP.
In practice
How FluentCRM work goes with an agent.
FluentCRM runs inside WordPress, so a contact is a row in its subscribers table with one of seven statuses, list and tag memberships in a pivot table, custom field values in meta rows keyed by field slug, and automations stored as funnels. The status decides what an agent may do: unsubscribed, bounced, complained and spammed contacts are suppressed. WP MCP reads straight from those tables but writes through FluentCRM's own API, so contact_added_to_lists and contact_added_to_tags still fire your automations, and FluentCRM's own permission sets gate each op.
Summarise our FluentCRM setup and tell me how new contacts are opted in.
Runs fluentcrm-summary: contact counts by status, lists, tags, campaigns and automations, the new-contact status (pending, with a double opt-in email), and whether campaign sending is switched on.
Find contacts with tag 12 who are still pending.
Runs fluentcrm-list-contacts with tag_id 12 and status pending, newest first, up to 100 per page. fluentcrm-get-contact then reads one by id or email with its lists, tags and custom fields.
Tag contact 41 with the Webinar tag and add them to list 3.
Runs fluentcrm-update-contact-tags and fluentcrm-update-contact-lists with add. Each is snapshotted, and the list add is refused if the contact has unsubscribed, bounced or complained.
Draft the November update campaign and send me a test.
Runs fluentcrm-create-campaign with a subject, HTML body and lists, which only saves a draft, then fluentcrm-send-test-campaign to the current user's own email. The draft can be undone; the test email cannot be unsent.
What your AI can do
Real FluentCRM operations, every write reversible.
- Read contacts, lists, tags, custom fields, campaigns and automations
- Create, update and delete a contact, with suppressed statuses never lifted
- Tag and untag contacts and add or remove them from lists
- Create, rename and delete lists and tags, and bulk-import contacts
- Create, update, duplicate, test and send or schedule a draft campaign
- Set an automation's status
- Roll back any write exactly, except a send, which cannot be unsent
Example prompts
Example FluentCRM prompts.
Add the tag "Webinar signup" to everyone on the Newsletter list.
Create a draft campaign for the November update and send me a test.
Import these 40 contacts and add them to the Customers list.
Under the hood
The FluentCRM calls, under the hood.
plugin-data-read({ integration: "fluentcrm", operation: "fluentcrm-list-contacts", args: { tag_id: 12, status: "subscribed" } }), queried from FluentCRM's tables
plugin-data-write({ integration: "fluentcrm", operation: "fluentcrm-send-campaign", args: {…} }), off until opt-in; confirms the recipient count; cannot be unsent
Safety and access
What can be undone on FluentCRM, and what costs what.
Recoverable on FluentCRM
- Contact, list, tag, campaign-draft and automation-status writes are each snapshotted as a CRM rows image, and rollback-operation restores them exactly.
- A contact or list delete puts the row back with its memberships; a list or tag delete is restorable up to 5000 members.
- rollback-session undoes a whole fluentcrm-import-contacts run, since each contact is its own snapshot.
- Rollback never sets anyone back to a mailable status.
FluentCRM limits and opt-ins
- fluentcrm-send-campaign is off until a site enables it with the wpmcp_enable_crm_send filter, asks for confirmation with the recipient count, and cannot be undone: mail cannot be unsent.
- fluentcrm-send-test-campaign sends only to the current user's email. It is snapshotted but its undo is refused.
- A new contact is created pending with a double opt-in email unless the site allows direct subscribes with wpmcp_crm_direct_subscribe. An email that already exists is refused, not merged.
- fluentcrm-import-contacts takes up to 100 contacts per call. fluentcrm-delete-contact and the list and tag deletes are destructive and need confirm:true.
Free or Pro: FluentCRM support is Pro, on the plugin-data pair, so it adds no top-level tools. Reads and the everyday writes (contacts, lists, tags, draft campaigns, automation status) need no switch beyond a licence and FluentCRM's own permissions, such as fcrm_read_contacts and fcrm_manage_contacts. Sending a campaign is the one opt-in, behind wpmcp_enable_crm_send. Deletes need confirm:true.
Part of WP MCP Pro
The FluentCRM integration is part of WP MCP Pro.
One Pro licence unlocks the FluentCRM tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.
Frequently asked
FluentCRM MCP: questions, answered.
Can the FluentCRM integration email people who did not opt in?
No. A new contact is created the way FluentCRM's own opt-in rules create one, pending with its double opt-in email, and a campaign goes only to subscribed contacts as FluentCRM counts them. A contact who unsubscribed, bounced or complained is refused from any list it would join.
Can a send be undone?
No. Mail cannot be unsent. A send or a test is snapshotted, but its undo is refused. Sending is also off until a site turns it on, and an unconfirmed send first answers with the recipient count through the confirmation path.
Which FluentCRM permissions does an op need?
WP MCP checks FluentCRM's own permission sets on top of the plugin-data pair's check, for example fcrm_read_contacts to read, fcrm_manage_contacts to write, fcrm_manage_contact_cats for lists and tags, fcrm_manage_emails for campaigns and fcrm_write_funnels for automations. A user without one gets operation_denied for that access.
What can an automation op do?
fluentcrm-list-automations shows each automation with its status and how many contacts are enrolled, and fluentcrm-set-automation-status sets it to published or draft through FluentCRM, which rebuilds its trigger index. That is snapshotted and reversible. Building or editing automation steps is not offered.
With FluentCRM, can the agent set a contact back to subscribed?
No. On an existing contact, unsubscribed is the one status a write can set, and FluentCRM's own update never lifts a suppressed status. A new contact can be created pending, or subscribed only where the site has allowed direct subscribes. Re-subscribing someone stays a decision for the contact.
How does a campaign pick its audience?
From the lists named in create-campaign or update-campaign, and only subscribed contacts, as FluentCRM counts them. A campaign with no lists has no recipients, and send-campaign refuses with no_recipients rather than sending to nobody. Only a draft can be edited, so a sent campaign is left alone.
Related integrations
More integrations for the same agent.
MCP for MailPoet
ProCRM & email, 2 tools.
MCP for Fluent Forms
ProForms, 6 tools.
MCP for Fluent Support
ProSupport, 2 tools.
MCP for FunnelKit
ProFunnels, 2 tools.
MCP for WooCommerce
FreeE-commerce, 9 tools.
MCP for WP Mail SMTP
FreeOperations, 2 tools.
Browse the full Integrations hub, or read more on FluentCRM MCP and the WordPress MCP plugin.