Triggers
Start runs the way your work starts.
Run a workflow by hand, on a schedule, whenever another system calls its webhook, or when a connected app reports a new record or event. Every run, however it started, lands in the same run history.
What you get
Four ways to start a run.
Manual
Press Run on the canvas. Good for prototyping and jobs someone kicks off on demand.
Schedules and cron
One-time, daily, weekly, monthly or a standard cron expression, in the timezone you pick. The cron field shows the next run time as you type.
App events
Start a run when something happens in a connected app: a new HubSpot deal, a new Google Sheets row, a Slack message. Most app events are checked on your plan's schedule interval; some arrive instantly by webhook.
Run windows
Limit schedules to allowed days and an optional time window, and set start and end dates.
Webhooks with secrets
Each workflow gets a fixed URL. Protect it with a secret header, an HMAC-SHA256 signature, or both.
Extra webhook checks
Optionally restrict callers to an IP allowlist, require specific headers, or use a vault credential as the secret.
Explicit activation
Configuring a trigger doesn't switch it on. You activate schedules and webhooks on purpose, and can disable them just as clearly.
Schedule speed by plan
How often schedules can run.
A scheduler checks every minute. Your plan sets the fastest a schedule may repeat.
| Plan | Schedules can repeat |
|---|---|
| Free | No live schedules (Dry Run only) |
| Basic | Every 15 minutes |
| Pro | Every 5 minutes |
| Business | Every 2 minutes |
| Elite | Every minute |
| Enterprise | Every minute |
Webhook security
Only the callers you expect.
Choose how each webhook checks the caller.
Shared secret
A token in a header (x-fluxo-secret by default).
HMAC signature
An HMAC-SHA256 of the raw body, signed with the secret.
Secret + signature
Both checks on every request.
IP allowlist and required headers
Optional extra checks on top of either mode.
Rotation
Regenerate the secret, or rotate the vault credential it uses.
Good to know
- Scheduled runs start within about a minute of their time.
- A generated webhook secret is shown once. To rotate it, regenerate the webhook and update your callers, or update the vault credential it uses.
- App event triggers start runs: polling events are checked on your plan's schedule interval, and instant events arrive by webhook where the app supports it. Most connected apps are in beta; each integration page shows which events it offers.
FAQ
Questions, answered.
How often can a schedule run?
It depends on the plan. Free: no live schedules (Dry Run only); Basic: every 15 minutes; Pro: every 5 minutes; Business: every 2 minutes; Elite: every minute; Enterprise: every minute. A schedule faster than your plan allows is refused when you activate it.
What happens to my schedules if I downgrade?
They keep running, slowed to the new plan's pace. Nothing is switched off.
How do I verify webhook calls?
Choose an auth mode on the trigger: a shared secret sent in a header, an HMAC-SHA256 signature of the raw body, or both. You can also add an IP allowlist and required headers.
Can I start a workflow from my own backend?
Yes. Give it a Webhook trigger, activate it, and POST JSON to its URL with the secret. The body is passed to the workflow as the trigger's output.
Put your first workflow on autopilot.
Build and Dry Run on the Free plan, no credit card. Run live on a paid plan, on your own AI key at cost.
Free to explore · No credit card · 30-day money-back guarantee on paid plans