What it does
A trigger is the event that starts a workflow. FlowWP listens to the actions WordPress and your plugins already fire, so a workflow can start the moment something happens on your site — not on a polling interval.
WordPress triggers
WordPress itself provides more than twenty triggers, including:
- A user is created, logs in, logs out, resets their password or is deleted
- A user’s role changes, or a specific role is added or removed
- A user publishes a post, or publishes a post in a taxonomy term
- A post is set to a specific status, or moved to the trash
- A comment is submitted, approved, or receives a reply
- A user’s meta key or a post’s custom field is updated
Plugins add their own: An order is paid in WooCommerce, A WPForms form is submitted, A user is enrolled in a LearnDash course, and many more across forms, LMS, membership, CRM and community plugins.
Beyond WordPress events
- A webhook is received — start a workflow from any outside system.
- On a schedule — run a workflow at a set time, with nobody present.
- Rows are imported from a file — turn each row of a CSV, JSON or XML file into a run.
How it works
FlowWP keeps an index of which triggers active workflows actually use, and only listens for those. When nothing is active, it binds no hooks at all. A post trigger fires on the transition into published, not on every save, so fixing a typo does not run the workflow again. And because WordPress sometimes fires the same hook twice, every trigger carries an idempotency key: the second firing is ignored instead of sending a second email.
Details
Everyday WordPress triggers are available on every plan. Precise triggers — a post updated with a specific term, a meta key set to a particular value — scheduled triggers and file imports are on Personal and above.
