Triggers
The four ways a workflow starts: webhook, schedule, manual, and platform events.
Every workflow begins with exactly one trigger. OpFlow has four.
Webhook
Generates a signed test URL and a production URL. Supports authentication — none, basic, header, or a query secret — and lets you choose how it responds: immediately, when the workflow finishes, or via a dedicated Respond node with a custom status and body.
Schedule
Cron-grade recurrence, down to the minute, backed by Postgres pg_cron. Set the rule and the workflow fires on its own.
Manual
Fire the workflow by hand from the workflow page — the fastest way to test end-to-end or run a one-off.
Platform events
First-party Opscend events — a form submission, a metric crossing a threshold (e.g. metrics.threshold_crossed), a traffic spike — trigger a workflow with zero webhook plumbing. This is the wedge no third-party tool has: OpFlow lives inside the same platform that emits the events.