Removes Google Analytics and Gravatar from the Pricing page, and documents exactly what Freemius receives. Nothing changes in how FlowWP works.<\/p>","1.2.1":"
Removes the last mentions of tracking parameters from the plugin's files. Nothing changes in how FlowWP works.<\/p>","1.2.0":"
A new name, no limits or usage counting of any kind, no tracking on links, and Action Scheduler 4.2.0. Connections to outside services move to FlowWP Pro.<\/p>","1.1.2":"
Updates the plugin's homepage link. Nothing changes in how FlowWP works.<\/p>","1.1.1":"
Includes the source of the editor and pricing page. Nothing changes in how FlowWP works.<\/p>","1.1.0":"
The free version no longer has caps: unlimited workflows, steps and runs, with AND \/ OR conditions, error paths and retries included.<\/p>","1.0.0":"
First public release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3750457,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3750457,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3750457,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3750457,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.2.2"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3750457,"resolution":"1","location":"assets","locale":"","width":1440,"height":962},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3750457,"resolution":"2","location":"assets","locale":"","width":1440,"height":860},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3750457,"resolution":"3","location":"assets","locale":"","width":1440,"height":626},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3750457,"resolution":"4","location":"assets","locale":"","width":1440,"height":900},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3750457,"resolution":"5","location":"assets","locale":"","width":1440,"height":787}},"screenshots":{"1":"The dashboard \u2014 what ran, what failed, and what you were last working on.","2":"The canvas \u2014 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.","3":"Your workflows: what each one connects and how often it has run.","4":"The template gallery \u2014 ready-made workflows, filtered by plan, category, and what this site actually has installed.","5":"Run history \u2014 every run, what started it, how long it took, and why one of them failed."}},"plugin_section":[],"plugin_tags":[569,16179,201155,286,8197],"plugin_category":[45],"plugin_contributors":[287118],"plugin_business_model":[],"class_list":["post-386763","plugin","type-plugin","status-publish","hentry","plugin_tags-automation","plugin_tags-integrations","plugin_tags-no-code","plugin_tags-woocommerce","plugin_tags-workflow","plugin_category-ecommerce","plugin_contributors-flowwp","plugin_committers-flowwp"],"banners":{"banner":"https:\/\/ps.w.org\/flowwp-workflow-automation\/assets\/banner-772x250.png?rev=3750457","banner_2x":"https:\/\/ps.w.org\/flowwp-workflow-automation\/assets\/banner-1544x500.png?rev=3750457","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/flowwp-workflow-automation\/assets\/icon-128x128.png?rev=3750457","icon_2x":"https:\/\/ps.w.org\/flowwp-workflow-automation\/assets\/icon-256x256.png?rev=3750457","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/flowwp-workflow-automation\/assets\/screenshot-1.png?rev=3750457","caption":"The dashboard \u2014 what ran, what failed, and what you were last working on."},{"src":"https:\/\/ps.w.org\/flowwp-workflow-automation\/assets\/screenshot-2.png?rev=3750457","caption":"The canvas \u2014 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."},{"src":"https:\/\/ps.w.org\/flowwp-workflow-automation\/assets\/screenshot-3.png?rev=3750457","caption":"Your workflows: what each one connects and how often it has run."},{"src":"https:\/\/ps.w.org\/flowwp-workflow-automation\/assets\/screenshot-4.png?rev=3750457","caption":"The template gallery \u2014 ready-made workflows, filtered by plan, category, and what this site actually has installed."},{"src":"https:\/\/ps.w.org\/flowwp-workflow-automation\/assets\/screenshot-5.png?rev=3750457","caption":"Run history \u2014 every run, what started it, how long it took, and why one of them failed."}],"raw_content":"\n
FlowWP watches for things happening on your site \u2014 an order, a form submission, a new member, a published post \u2014 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.<\/p>\n\n
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.<\/p>\n\n
Every value produced by an earlier step is available to a later one as a token \u2014 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.<\/p>\n\n 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.<\/p>\n\n FlowWP adds steps for the plugins it finds installed, and says so plainly when one is missing rather than hiding it:<\/p>\n\n 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.<\/p>\n\n 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.<\/p>\n\n The editor and the pricing page are JavaScript, shipped minified in To rebuild both from the plugin's folder, with Node.js 24 or later:<\/p>\n\n FlowWP has paid plans that add steps and features the free version does not include \u2014 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 \u2014 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.<\/p>\n\n 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.<\/p>\n\n Freemius<\/strong> (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:<\/p>\n\n Freemius: Terms of service<\/a> \u00b7 Privacy policy<\/a><\/p>\n\n 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.<\/p>\n\n\n FlowWP needs WordPress 6.5 or newer and PHP 8.1 or newer.<\/p>\n\n\n 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 \u2014 see \"External services\" above.<\/p><\/dd>\n No. A new workflow is a draft. It does nothing at all until you activate it, and deactivating it stops it immediately.<\/p><\/dd>\n 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 \u2014 a sent message, a created order \u2014 are marked so the engine never retries them for you.<\/p><\/dd>\n Yes. Retries \u2014 and, on the paid plans, delays and scheduled workflows \u2014 go through Action Scheduler, which WordPress plugins have used for this for years. A workflow waiting three days does not hold a request open.<\/p><\/dd>\n 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.<\/p><\/dd>\n Yes. Deactivating stops workflows running and changes nothing else. Deleting the plugin only removes your data if you explicitly ask it to \u2014 the default is to leave everything where it is.<\/p><\/dd>\n Yes. FlowWP registers with WordPress' own Tools \u2192 Export Personal Data<\/strong> and Erase Personal Data<\/strong>, so a request made there covers FlowWP's run history alongside everything else.<\/p>\n\n 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 \u2014 deleting that would stop an automation working, so FlowWP names the workflow and leaves the decision to you.<\/p><\/dd>\n 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.<\/p><\/dd>\n\n<\/dl>\n\n\n The free version has no caps.<\/p>\n\n First public release.<\/p>\n\n{{ trigger.order.email }}<\/code>, {{ nodes.lookup.output.name }}<\/code> \u2014 with a picker so you do not have to remember them.<\/p>\n\nYou can see what happened<\/h4>\n\n
What the free version includes<\/h4>\n\n
\n
Works with what you already have<\/h4>\n\n
Built to be extended<\/h4>\n\n
Source code<\/h4>\n\n
admin\/dist<\/code> and assets\/freemius-pricing<\/code>. Their full source is included in the plugin: admin\/src<\/code> (TypeScript and React, built with Vite) and pricing-app\/src<\/code> (React, built with webpack), with the package.json<\/code> and lock files that pin every dependency.<\/p>\n\nnpm ci\nnpm run build\n\nnpm ci installs the dependencies for both, and `npm run build` type-checks the editor and writes `admin\/dist` and `assets\/freemius-pricing`.\n<\/code><\/pre>\n\nPremium<\/h4>\n\n
External services<\/h4>\n\n
\n
\n
\n
Does this send my site's data to a third party?<\/h3><\/dt>\n
Does anything run before I want it to?<\/h3><\/dt>\n
What happens when a step fails?<\/h3><\/dt>\n
Can it handle things that take a while?<\/h3><\/dt>\n
Is the free version limited?<\/h3><\/dt>\n
Will my workflows survive deactivating the plugin?<\/h3><\/dt>\n
Someone has asked me to export or delete their data. Does FlowWP help?<\/h3><\/dt>\n
Can I add my own steps?<\/h3><\/dt>\n
1.2.2<\/h4>\n\n
\n
1.2.1<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
flowwp_history_retention_days<\/code> filter.<\/li>\n1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
admin\/src<\/code> and pricing-app\/src<\/code>, with the build files and lock files that rebuild the minified editor and pricing page. See \"Source code\" above.<\/li>\n<\/ul>\n\n1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n