Questions, answered plainly

FlowWP is a visual workflow automation platform built specifically for WordPress. You connect a trigger, such as a paid WooCommerce order, a form submission, a new user or a webhook, to conditions and actions on a canvas, and the workflow runs inside WordPress on your own server, with every run recorded step by step. The free plugin has no caps on workflows, steps or runs; FlowWP Pro adds loops, delays, scheduling, the AI workflow builder and hundreds of integration steps.

No. You build workflows by dragging steps onto a canvas and joining them up, and a picker lists every value earlier steps produced. Developers can go further by registering their own steps or PHP functions.

Yes, in FlowWP Pro. Describe what should happen in your own words and FlowWP builds it from the steps your site has, using your own Claude, OpenAI or Gemini key. You get a draft to review, with anything only you can decide listed for you, and nothing is saved until you keep it. It is included on every paid plan, with no daily limit.

No. Workflows run on your own server, on WordPress’ own hooks. The free plugin contacts no outside service on its own: only an HTTP Request step sends data, to the address you give it, and Freemius handles plans and licences. FlowWP Pro adds connections to services such as Slack or Mailchimp, which are contacted only when a workflow uses them.

No. A new workflow is a draft and does nothing until you activate it. Deactivating it stops it immediately, and a test run rehearses steps that would change something instead of doing them.

The run stops and is recorded with the step that failed and why. A step that is safe to repeat can be retried automatically, on every plan; a sent message or a created order never is. From the run history you can run any finished execution again with the data it started with.

Delays, scheduled workflows and retries all go through Action Scheduler, so a workflow waiting three days does not hold a request open and visitors never wait on your automation.

WordPress itself, WooCommerce, the major form, LMS, membership and CRM plugins and, in FlowWP Pro, Slack, Discord, Telegram, WhatsApp, Mailchimp and AI providers. FlowWP adds steps for the plugins it finds installed and says plainly when one is missing.

Yes. The free plugin does not expire and has no caps: unlimited workflows, steps and runs, AND / OR conditions, On error paths and retries, and 30 days of run history, with the visual editor and run inspector included. Paid plans come as FlowWP Pro and add steps and features.

Letting your site carry out repetitive work by itself. When something happens — an order is paid, a form is sent, someone signs up — a workflow runs the steps a person would otherwise do: send an email, update a CRM, tell the team.

Not with FlowWP. You build workflows by joining steps on a canvas, start from a ready-made template, or describe what you want and let the AI builder draft it. Developers can add their own steps in PHP, but nobody has to.

Whatever starts on your site and follows the same steps each time: orders, form entries, sign-ups, memberships, course progress, new posts and comments. Each integration page lists the exact triggers and actions FlowWP adds for that plugin or app.

Workflows start on WordPress’ own hooks, and anything that waits — a delay, a schedule, a retry — goes through Action Scheduler in the background. A visitor never waits for a workflow that pauses for three days.

A plugin runs inside WordPress and acts on the site directly. A platform like Zapier or n8n runs outside it and reaches the site through its API and webhooks. Our comparison pages go through the differences in detail.

Yes. FlowWP’s free version does not expire and has no caps: unlimited workflows, steps, runs and webhooks, with 30 days of run history.

Yes, and it is not a trial: it does not expire or count down. It has no caps — unlimited workflows, steps, runs, webhooks and HTTP requests — with AND / OR conditions, On error paths, retries, 30 days of run history, the visual editor and the run inspector.

No. Nothing in it stops at a number. The paid plans add steps and features the free version does not include — loops, delays, Switch, scheduled triggers, the AI builder and hundreds of integration steps — rather than lifting limits on what it already does.

Personal covers 1 site, Business 5 and Agency 25. The number of sites is applied when you activate your license on a site.

Yes. The AI workflow builder and the AI steps use your own Anthropic, OpenAI or Google key, so the provider bills you directly for what you use. The AI builder is part of FlowWP Pro on every paid plan, with no daily limit.

No plan, Free included, limits workflows, steps, runs, webhooks or HTTP requests. FlowWP counts runs and requests so the dashboard can show them, but nothing stops at a count. Workflows run on your own server, so your hosting is the only ceiling.

Yes. Plans build on each other — Business includes everything in Personal, and Agency everything in Business — and the workflows you have already built keep working when you upgrade.

Workflows run on your own server and there is no account to create to use them. Licensing and updates are handled by Freemius, and sharing anonymous usage data with it is optional.

No. Steps other plugins register work on every plan, and a step with no feature key runs on every plan including Free. If you want a step on a paid plan only, declare your own feature with register_feature(). A site’s own PHP functions offered as steps are part of the Agency plan.

No. There is no “Run PHP” box. A site offers functions to FlowWP from PHP, a workflow stores only the function’s name, and the callable comes from the site at run time.

The published contracts do not change incompatibly without FlowWP::SDK_VERSION changing with them. Everything outside them is internal. Never rename a step’s type: saved workflows store it.

Declare a connection type with register_credential_type(). FlowWP encrypts the values, never sends secret fields back to the browser, and keeps them out of API responses and workflow exports. Your step reads them with $context->credential().

Mark it writes: true and give it a preview. A test run in the editor then shows what the step would have done instead of doing it.

Whenever you like: from your plugin’s main file, on plugins_loaded, or in a callback of your own. FlowWP works out whether the registry you are adding to exists yet and waits for it if it has to.