Prepare a FluentCRM email campaign
Create a campaign draft, preview it and check an explicitly requested test email.

Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- EMCP Pro, a connected practice site and the supported plugin active.
- Permission to edit the plugin and fictional practice records.
- FluentCRM 3.x, its MCP access enabled and a sender/test inbox you control.
Let’s do this, step by step.
Step 01
Enable and inspect the integration
Open EMCP Tools → Tools → Plugins → FluentCRM. Check dependencies and Read/Write switches, enable needed actions and Save changes. Reconnect and request get-setup.
Open EMCP Tools, Tools, then Plugins. Find FluentCRM, check its requirements and enable the actions needed here. Choose Save changes and reconnect. Ask the AI to read the setup before changing anything.
Step 02
Enable FluentCRM access
If get-setup reports fluentcrm_mcp_disabled, enable FluentCRM → Settings → MCP. Check sender settings.
FluentCRM has its own access switch. If setup reports it off, open FluentCRM, Settings, then MCP and enable it. Recheck the sender and test inbox.
Step 03
Choose a practice audience
Read lists and tags; preview imports with dry_run. Keep run_automations false and preserve consent.
Read lists and tags and choose a small practice audience. Keep automations off. Adding a tag or list should not unexpectedly start a sequence or change consent.
Step 04
Create and preview
Create a campaign draft using live schemas; read get-campaign, preview-email and inspect the native editor.
Create a draft with your subject, message and chosen audience. Preview it and check links, sender and layout in FluentCRM. Keep it unscheduled.
Step 05
Test only when requested
An explicitly approved send-test-email needs confirmation and goes to the connected user’s own address. Verify inbox delivery.
When ready, request and confirm one test email to your own address. Check the actual inbox and links. A saved draft alone does not prove delivery.
Step 06
Review before scheduling
A production schedule needs matching recipients_estimate/expected_recipients, confirmation and site-local time. Do not schedule in rehearsal.
Before a real schedule, read and confirm the current recipient count. Use the site’s local time. A changed count needs a new review. Once messages leave the queue, undo cannot bring them back.
You’re done when…
The campaign remains a reviewed draft; any requested test is verified and no audience send is scheduled.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.
A brief becomes a real page.