Skip to content
FlowWP logo
Menu

About FlowWPv1.2.2

FlowWP, the WordPress automation plugin

FlowWP is a WordPress plugin for building automations visually. It runs inside WordPress, on your own server, with no external service in the middle.

Build automations visually. Connect a trigger to conditions and actions on a canvas, and let your site do the work you were doing by hand.

FlowWP watches for things happening on your site — an order, a form submission, a new member, a published post — and does what you would otherwise have done yourself. You build it by dragging steps onto a canvas and joining them up. Nothing runs until you activate it.

It runs inside WordPress. There is no external service in the middle, no per-task pricing, and no account to create: your workflows execute on your own site, on WordPress' own hooks, using Action Scheduler for anything that needs to happen later.

Features

What the plugin does

From the event that starts a workflow to the record of what it did.

  • When something happens

    A WooCommerce order is paid, a form is submitted, a user registers or changes role, a post is published, a comment arrives, or a webhook is called. The paid plans add scheduled times and more triggers.

  • Decide what to do about it

    Branch on any value with If, or stop a run that does not qualify with Filter, with as many AND / OR rules as you need. The paid plans add Switch, to split several ways.

  • Then do it

    Send an email, call an external API, update a custom field, add a note to an order, or use one of the steps a plugin you already have contributes. The paid plans add creating and updating posts, changing roles, and more.

  • Every value, ready for the next step

    Every value produced by an earlier step is available to a later one as a token — {{ trigger.order.email }}, {{ nodes.lookup.output.name }} — with a picker so you do not have to remember them.

  • You can see what happened

    Every run is recorded: which steps ran, what each was given, what each returned, and where it stopped if it stopped. A failed step can be retried on its own rather than re-running the whole thing. This is usually the difference between an automation you trust and one you turn off.

  • Built to be extended

    Node types, triggers, conditions and actions are all registered through a documented contract, so another plugin can contribute its own steps without touching FlowWP. Registered functions let a developer expose a PHP function to workflow authors safely.

Screenshots

Inside the plugin

The plugin’s own screens, as they appear in wp-admin.

The dashboard — what ran, what failed, and what you were last working on.
1The dashboard — what ran, what failed, and what you were last working on.
The canvas — a trigger joined to a condition and three actions, the step library on the left, and the step being configured on the right with a picker for every value earlier steps produced.
2The canvas — a trigger joined to a condition and three actions, the step library on the left, and the step being configured on the right with a picker for every value earlier steps produced.
Your workflows: what each one connects and how often it has run.
3Your workflows: what each one connects and how often it has run.
The template gallery — ready-made workflows, filtered by plan, category, and what this site actually has installed.
4The template gallery — ready-made workflows, filtered by plan, category, and what this site actually has installed.
Run history — every run, what started it, how long it took, and why one of them failed.
5Run history — every run, what started it, how long it took, and why one of them failed.

Installation

Running in a few minutes

FlowWP needs WordPress 6.5 or newer and PHP 8.1 or newer.

  1. 1

    Install and activate the plugin.

  2. 2

    Open FlowWP in the admin menu. The dashboard offers two ways to start: a ready-made template or a blank canvas.

  3. 3

    Build a workflow, then press Activate. Nothing runs until you do.

  4. 4

    Watch the first few runs under Run history to see exactly what happened.

Free & premium

Free to start, and it stays free

Build and run your first workflows for free, on one site. Upgrade when your workflows need more.

What the free version includes

  • As many workflows as you want, with as many steps as each one needs
  • Unlimited runs, webhooks and HTTP requests — nothing stops at a monthly count
  • Every free step, including If, Filter, AND / OR conditions, On error paths and retries
  • Every ready-made template built from those steps
  • 30 days of run history
  • The visual editor and the run inspector

There are no caps in the free version and nothing in it is a trial: it does not count down, expire, or stop after a number of runs.

Paid plans

FlowWP has paid plans that add steps and features the free version does not include — loops, delays, Switch, scheduled triggers, more condition operators, the messaging and marketing integrations, the AI steps and the AI workflow builder, file imports, workflow import and export — and keep run history for longer on the Business and Agency plans. They add to the free version rather than lifting limits on it: everything listed under "what the free version includes" keeps working, unchanged, whether or not you ever upgrade.

Privacy

External services

Apart from Freemius, below, the plugin contacts no outside service on its own and loads no analytics. It has no connections to one either: the connections to Slack, Discord, Telegram, WhatsApp, Mailchimp and the AI providers are part of FlowWP Pro and are not included in it.

  • Freemius

    Freemius (freemius.com, including api.freemius.com, checkout.freemius.com, img.freemius.com and wp.freemius.com) runs FlowWP's plans, checkout and licences. FlowWP talks to it only in these cases:

    If you opt in when activating FlowWP
    Nothing is sent if you skip. If you allow it, Freemius receives your WordPress user's first and last name and email address; the site's homepage address and title, WordPress and PHP versions and language; the FlowWP and Freemius SDK versions, and whether FlowWP is active or uninstalled; and, if you leave that option on, the names, slugs and versions of your plugins and themes. Freemius uses it to send security and product updates and to keep FlowWP compatible with your site.
    When you open the Pricing page
    The site asks Freemius for FlowWP's current plans and prices, identifying FlowWP and, if this site has opted in, the site's Freemius account. The page shows Freemius's loading image, from img.freemius.com.
    When you buy a plan
    Choosing a plan opens Freemius's checkout, at checkout.freemius.com, which receives the plan you chose and what you enter there, such as your name, email address and payment details.
    When you activate a licence key
    The key is sent to Freemius with the site's homepage address, the FlowWP version and the SDK version, so the licence can be checked and kept to the sites you allow.
    When you write to us through FlowWP's Contact page
    The form is Freemius's, from wp.freemius.com, and it receives what you type into it.

    Terms Privacy

The HTTP Request step sends data to whatever address you give it. That address is yours, not ours, and FlowWP neither chooses it nor sees the response.

FAQ

Questions about the plugin

How it handles your data, failures, limits and deactivation, from the plugin’s own readme.

Read the documentation
Does this send my site's data to a third party?

No. Workflows run on your own server, and the plugin contacts no outside service on its own. It sends something elsewhere only when a workflow uses the HTTP Request step, to the address you give it, or through Freemius: when you open the Pricing page, or if you opt in to anonymous usage data when activating — see "External services" above.

Does anything run before I want it to?

No. A new workflow is a draft. It does nothing at all until you activate it, and deactivating it stops it immediately.

What happens when a step fails?

The run stops and is recorded with the step that failed and why. You can retry that step on its own, and steps that would be unsafe to repeat — a sent message, a created order — are marked so the engine never retries them for you.

Can it handle things that take a while?

Yes. Retries — and, on the paid plans, delays and scheduled workflows — go through Action Scheduler, which WordPress plugins have used for this for years. A workflow waiting three days does not hold a request open.

Is the free version limited?

No. There is no cap on workflows, steps, runs, webhooks or HTTP requests, and nothing in it is a trial. The paid plans add steps and features the free version does not contain; they never lift a limit on what it already does.

Will my workflows survive deactivating the plugin?

Yes. Deactivating stops workflows running and changes nothing else. Deleting the plugin only removes your data if you explicitly ask it to — the default is to leave everything where it is.

Someone has asked me to export or delete their data. Does FlowWP help?

Yes. FlowWP registers with WordPress' own Tools → Export Personal Data and Erase Personal Data, so a request made there covers FlowWP's run history alongside everything else.

Two things it deliberately does not delete, and tells you about rather than hiding: a run still in progress, which the ordinary history sweep removes once it finishes, and a workflow whose own setup contains that address — deleting that would stop an automation working, so FlowWP names the workflow and leaves the decision to you.

Can I add my own steps?

Yes. Nodes are registered through a documented contract, so a plugin or a site's own code can add triggers, conditions and actions that behave exactly like the built-in ones.

Changelog

The latest release

Full changelog

1.2.2

Removes Google Analytics and Gravatar from the Pricing page, and documents exactly what Freemius receives. Nothing changes in how FlowWP works.

  • The Pricing page no longer loads Google Analytics, which came with the Freemius pricing page it is built on, or reviewers' pictures from Gravatar.
  • External services describes exactly what Freemius receives and when.
  • Every REST route checks the user's capability where the route is registered.

Build your WordPress workflow visually.

Start with a template or a blank canvas. Nothing runs until you activate it.