Trigger a workflow from MCP Tool and check user details in FluentCRM

Give your AI assistant a FluentCRM lookup: it calls this workflow’s MCP tool with an email, FlowMattic retrieves that contact from FluentCRM and sends the details you choose back as the tool’s answer.

FlowMattic MCP

FluentCRM

Download this workflow Browse more workflows

3 steps Setup ~5 min Used on 3.2k sites Free to import

The Trigger a workflow from MCP Tool and check user details in FluentCRM workflow on the FlowMattic canvas, with 3 steps across FlowMattic MCP, FluentCRM — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Support and sales chats often start with a question like "is this person already a customer?" Instead of switching to the WordPress dashboard, you can let your AI assistant check FluentCRM for you. This workflow turns a FluentCRM contact lookup into an MCP tool the assistant can call during a conversation.

The FlowMattic MCP trigger runs when the MCP tool tied to this workflow is executed. To create it, save the workflow and add a tool on the FlowMattic MCP Server page with Workflow as its execution method and this workflow selected. Give the tool an input parameter for the email address, since that is what the lookup needs.

Next, the FluentCRM step retrieves a contact by email. It ships unmapped, so map the tool's email parameter into it. The last step, MCP Tool Response, returns key and value pairs to the assistant. It is empty as imported, and FlowMattic answers with an error when there are no response parameters, so add the fields the assistant should see, such as the contact's name, status, tags or lists from step 2.

Only send back what the assistant needs. Every value in the response becomes part of the AI conversation.

Checking a subscriber during support

A support agent asks the assistant whether a customer's email is subscribed, and the tool replies with the contact's FluentCRM status before the agent answers the ticket.

Lead context for sales calls

A consultant asks an AI client which tags a prospect has in FluentCRM, so she knows which lead magnet they downloaded before the call starts.

Agent that personalises replies

An AI agent drafting email replies looks the sender up through this tool first and greets them by the first name stored in FluentCRM.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
FlowMattic MCP Workflow MCP Tool Triggered
Starts whenever the assistant calls this workflow's MCP tool. The input parameters you set on the tool, typically an email address, are passed to FluentCRM.
Step 2Action
FluentCRM Get Contact by Email
Looks up the FluentCRM contact that has the email the assistant sent. The step arrives empty, so map the tool's email parameter here, then call the tool once to see which fields come back.
Step 3Action
FlowMattic MCP MCP Tool Response
Sends the chosen contact details back to the AI client as key and value pairs. The template has none; add fields such as name, status and tags from the FluentCRM step.

What you need

FlowMatticCore
FluentCRM PluginPlugin

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Describe the email parameter on the MCP tool clearly, for example "Email address of the contact to look up", so the assistant passes the right value.
Include the FluentCRM contact ID in the MCP Tool Response, so the assistant can tell which record its answer came from.
Leave out sensitive fields, such as phone numbers or custom notes, unless the assistant needs them for its task.

Questions about this workflow

What does the assistant get if the email isn't in FluentCRM?

FluentCRM has no contact to return for that address. Call the tool with an unknown email and check Task History to see what the lookup step returned and what reached the assistant.

Must FluentCRM run on the WordPress site that hosts this MCP workflow?

Yes. The Get Contact by Email step reads from the FluentCRM plugin on the WordPress site where this workflow runs.

Can the assistant change FluentCRM contacts with this tool?

No. The workflow only retrieves a contact and returns its details. Editing contacts would need a separate tool and workflow with a FluentCRM update action.

Which FluentCRM fields reach the AI client?

Only those you add to the MCP Tool Response step. The step ships empty, so pick each field from the lookup result and give it a key the assistant can understand.