FlowWP – Visual Workflow Automation

Description

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.

What you can build

• 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 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.

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.

Works with what you already have

FlowWP adds steps for the plugins it finds installed, and says so plainly when one is missing rather than hiding it:

WooCommerce, WPForms, Gravity Forms, Fluent Forms, Formidable Forms, Ninja Forms, Forminator, Contact Form 7, Elementor, Advanced Custom Fields, LearnDash, Tutor LMS, LearnPress, LifterLMS, MemberPress, Paid Memberships Pro, Ultimate Member, BuddyPress, GamiPress, FluentCRM, Groundhogg, MailPoet, Easy Digital Downloads, GiveWP, The Events Calendar. FlowWP Pro adds Slack, Discord, Telegram, WhatsApp, Mailchimp and the major AI providers, which need a connection rather than a plugin.

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.

Source code

The editor and the pricing page are JavaScript, shipped minified in admin/dist and assets/freemius-pricing. Their full source is included in the plugin: admin/src (TypeScript and React, built with Vite) and pricing-app/src (React, built with webpack), with the package.json and lock files that pin every dependency.

To rebuild both from the plugin’s folder, with Node.js 24 or later:

npm ci
npm run build

npm ci installs the dependencies for both, and `npm run build` type-checks the editor and writes `admin/dist` and `assets/freemius-pricing`.

Premium

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.

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.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.

Freemius: Terms of service · Privacy policy

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.