A visual workflow builder for WordPress
Chain a trigger, your apps and real logic on one canvas, inside the WordPress site you already run. Every workflow you build is yours to run as often as you like: there is no per-task fee and nothing leaves your server unless you send it.
918+ integrations60+ built-in modulesUnlimited workflows and runsRunning on 12,939+ sites
Three steps from idea to running automation
The builder keeps the order you think in: what starts it, what happens, and whether it worked.
-
Trigger
Pick what starts it
A WordPress event, a WooCommerce order, a form submission, a webhook, a schedule or an app event from any of the 918+ integrations. Capture a sample so every later step can map real fields.
-
Steps
Add apps and logic
Each step is an action in an app or a module: Router, Filter, Iterator, Delay, Join, API call, PHP function. Fields are filled by picking data from earlier steps, so nothing is typed twice.
-
Run
Test, switch on, watch
Test any step against captured data before the workflow goes live. Once it is on, Task History records every run with the data in and out of each step, and lets you replay one.
Logic that reads like the process it automates
A Router splits a run into named branches, each gated by its own Filter. Branches can rejoin with a Join step so the rest of the workflow runs once. Iterator loops over line items or table rows, Delay waits for a duration or a date, and a Sub-workflow call keeps big processes modular.
- Router and Branch for multi-path decisions
- Filter conditions on any field, with AND and OR groups
- Iterator for arrays and record sets, with a wait between items
- Delay for a duration or until a date, in any time zone
- Human in the Loop approval by email before a branch continues
Every field, filled from the data you already have
Open a step and the panel walks through Setup, Configure, Conditions and Test. Any field accepts dynamic data from the trigger or an earlier step, picked from a list rather than typed. Conditions let a single step run only when it should, and Test runs the step for real against the captured sample.
- Dynamic tags for every field, with the captured response beside them
- Per-step conditions, so a step can skip without a Router
- Test a step on its own and see the exact response
- Long step names wrap on the canvas; hover shows the full name
Describe it, and Jaadu builds it on the canvas
Jaadu is the AI copilot inside the builder. Tell it what you want in plain language and it picks the apps, adds the steps, wires the fields and fixes what breaks. You stay on the same canvas and can edit anything it made.
See every run, step by step, and replay it
Task History keeps every run with the inputs each step received and the response it returned, secrets masked. A failed run can be re-executed with its original data or with an edited payload, and a run's trigger data can be loaded back into the builder for mapping.
Built-in modules for the parts no app covers
Sixty-plus modules ship with the plugin. These are the ones most workflows reach for.
Webhooks
Catch any webhook, verify the sender's signature, send outgoing webhooks and reply with any status code.
Scheduler
Every few minutes, hourly, daily, weekly or monthly, with weekend control and an optional Cloud wake for quiet sites.
Router, Filter, Join
Branch on conditions, stop a run early, and bring paths back together.
Iterator and Delay
Loop over items with an optional pause between them; wait for a duration or until a date.
AI Agent
Give a step a goal and the tools it may call; it reasons through the task with your own API key.
Human in the Loop
Pause until someone approves or rejects by email, then continue on the answer.
Data tools
Format text, dates and numbers, parse JSON, XML, CSV and PDFs, do maths, encrypt and sign values.
API and Custom Apps
Call any REST endpoint mid-workflow, or turn a whole API into a reusable app from its OpenAPI spec.
PHP Function
Drop to code for the one transformation no module covers, and pass its result to the next step.
Workflows people actually run
Each of these is a real workflow built in the builder shown above. The library has 4,676 more you can import.
New order, triaged by AI, routed to the right team
WooCommerce new order, then an AI Agent classifies it, a Router sends priority orders to Slack and standard orders a confirmation email, and the customer is added to FluentCRM either way.
Refund request with a manager's approval
A Form Builder submission waits on a Human in the Loop email. Approved requests notify finance in Slack and confirm to the customer; rejected ones send the manager's note.
Daily invoices from a table
A 09:00 schedule reads unpaid rows from WP Tables, loops through them, renders a PDF invoice for each, emails it and logs the send in Google Sheets.
Published post, announced everywhere
A new WordPress post goes to an AI Agent that writes the social copy, which lands in the team's Telegram chat and on the content calendar in Google Sheets.
Questions about the builder
Do I need to write code to build a workflow?
No. Triggers, actions and logic modules are configured in forms, and fields are filled by picking data from earlier steps. A PHP Function module exists for the rare transformation no module covers, but most workflows never use it.
How many workflows can I build, and how often can they run?
As many as you need. Every FlowMattic plan includes unlimited workflows and unlimited runs. The only thing a plan changes is how many sites you can activate it on.
Where do my workflows run?
On your own WordPress server. Triggers fire inside WordPress, steps run there, and credentials stay in your own site database, masked wherever Task History shows them. Only the requests you configure, such as a call to Slack or an AI provider, leave the server. FlowMattic Cloud is optional and only relays webhooks and schedule timings for you.
Can a workflow have more than one trigger?
Yes. Add further triggers to the same workflow and map each trigger’s fields onto the first one’s names, so the rest of the workflow keeps working whichever event started it.
What happens when a step fails?
The run is recorded in Task History as failed, with the inputs the step received and the response it got back. You can fix the cause and re-execute the run with its original data, or edit the data first.
Can I import workflows other people built?
Yes. The workflow library holds importable workflows built by the FlowMattic team, and any workflow can be exported as JSON and imported on another site.
Did not find your answer? You can browse the help center or ask us directly.
Build your first workflow this afternoon
Try the builder on a live demo site, or install FlowMattic on your own and keep every run on your server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted