Trigger a workflow from MCP Tool and create custom polls in FluentCommunity
Give your AI assistant an MCP tool that creates polls in your FluentCommunity feed: when the tool is called, FlowMattic posts a new poll with the question and options the assistant sends.
FlowMattic MCP
Fluent Community2 steps Setup ~5 min Used on 3.0k sites Free to import
What this workflow does
Community managers run polls to pick webinar topics, test ideas or just get members talking. Writing each one in the FluentCommunity editor takes a few minutes; asking an AI assistant to draft and post it takes one message. This workflow exposes poll creation as a tool on your FlowMattic MCP server, so Claude or another MCP client can post polls for you.
A run starts whenever an assistant calls the poll tool that the FlowMattic MCP trigger defines for this workflow. The values the assistant passes with the call, such as a question and a set of answer options, become available to the next step. Define those inputs on the tool so the assistant knows what to send.
The FluentCommunity Create New Poll in Feed step then creates the poll in your community feed. It ships unmapped: after import, map the values from the MCP call into the poll and review the step's other options. Run a test call and check the feed and Task History to see the result.
The template has no MCP Tool Response step, so the assistant isn't told what was created. Add one after the poll step if you want it to receive the result.
Weekly engagement poll
A community manager asks Claude every Monday to write a light poll for members and post it to the feed through this tool.
Choosing the next workshop topic
A course creator has the assistant post a poll listing three workshop ideas, then plans the session around the winning answer.
Quick feedback on a product change
A SaaS company's community lead posts a poll asking members how they find a new feature, drafted by the assistant from the release notes.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
FlowMattic MCP Workflow MCP Tool TriggeredStarts when the MCP tool tied to this workflow is executed by your AI assistant. The values it sends with the call, such as the poll question and options, become available to map.
- Fluent Community Create New Poll in Feed
Creates a new poll in your FluentCommunity feed. The step ships without mapping, so after import you map the question and options from the MCP call and check the step's remaining settings.
What you need
- FlowMatticCore
- FluentCommunity 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.
- Add an MCP Tool Response step after the FluentCommunity step and map the poll details it returns, so the assistant can confirm what it posted.
- Put a Human in the Loop approval between the MCP trigger and the FluentCommunity step if a person should check each poll before members see it. Set its timeout action to End Workflow.
- Describe the tool's inputs plainly, such as one question and a list of options, so the assistant sends values that fit the poll step.
Questions about this workflow
Which AI assistants can use this FluentCommunity poll tool?
Any client connected to your FlowMattic MCP server, such as Claude. The assistant decides when to call the tool based on its description and your request.
Does the assistant get confirmation that the poll was posted?
Not as imported, because there is no MCP Tool Response step. Add one after the poll step and map the result into it.
Can I review the poll before it appears in FluentCommunity?
Yes, if you add a Human in the Loop step before the poll step. A rejection ends the run, so nothing is posted.
More AI Automation workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted