Triggers

A trigger is the first node in every workflow. It defines what starts the workflow.

Categories of triggers

1. WordPress hook triggers — fire when a specific WP action or filter runs. Most common: post saved, user registered, comment posted. The complete list of WP-hook triggers is in the WordPress hooks integration.

1. WooCommerce triggers — fire on order, product, customer, refund and subscription events. See WooCommerce integration.

1. Form submission triggers — fire when a form plugin records a submission. Supports Gravity Forms, Contact Form 7, WPForms, Fluent Forms, Forminator, Ninja Forms. See Forms integration.

1. Schedule triggers — fire on a cron-like schedule. Granularity down to 1 minute on systems with WP-Cron running externally.

1. Incoming webhook triggers — fire when an external system POSTs to a dedicated URL the workflow exposes.

1. Manual triggers — fire only when an admin presses Run now in the editor. Useful for one-off jobs and for testing.

1. WP-PFManagement record triggers — fire on pfm.record.created, .changed, .deleted, etc. when an entity record changes. Requires WP-PFManagement installed.

Trigger payload

Every trigger produces a typed payload that downstream nodes can reference with token syntax {{trigger.field_name}}. The exact fields depend on the trigger; each trigger's page in the Nodes catalog lists them.

One trigger per workflow

A workflow has exactly one trigger. If you need the same downstream logic for two different triggers, either:

• Build it as a callable function workflow that two trigger-only workflows call.
• Use the Manual run trigger plus an Incoming webhook trigger in two parallel workflows that both point at the same library workflow.