A trigger is what starts a workflow. Every workflow has at least one. Some you press yourself; others run automatically when something happens somewhere else - a new Gmail message arrives, a Google Sheet row is added, the clock hits 8 AM, or an outside system sends you a notification.
One workflow, many triggers
A workflow can have more than one trigger. You might run it manually while building it, put it on a daily schedule once it's ready, and also let a Slack mention kick it off - all at the same time.Trigger Types
ORCFLO has four trigger types. Pick whichever matches how you want the workflow to start.
| Trigger | Starts when | Good for |
|---|---|---|
| Manual | You click Run | Building and testing, one-off tasks, anything you start yourself |
| Scheduled | A time or cron schedule fires | Daily summaries, hourly sync jobs, weekly reports |
| Webhook | An outside system POSTs to your webhook URL | Custom systems, Zapier, internal tools, anything that can send HTTP |
| App | Something changes in a connected app | New Gmail messages, new Drive files, new Sheets rows, and more |
Passing Data to Your Workflow
When a trigger fires, it usually brings information with it - the subject of the new email, the row that was added, the body of the incoming webhook. You choose which of those pieces become inputs your workflow can use.
During trigger setup you'll see a list of available fields from the event. Tick the ones you want, give each a friendly name, and they become variables like ${inputs.subject} that you can reference anywhere in your workflow - in prompts, conditions, or outputs.
Test before you launch
Webhook triggers include a test mode: flip it on, send a real event from the outside system, and ORCFLO shows you the exact payload so you can map fields with confidence before going live.Choosing the Right Trigger
Is the app already in our integrations list?
Use an app trigger. It's the shortest path - connect the app, pick an event, done.
Is it a custom system or an in-house tool?
Use a webhook trigger. Copy the URL and signing secret into the other system and you're connected.
Does it need to run on a clock?
Use a scheduled trigger. Good for daily digests, hourly polls, and anything that has to happen even when nobody triggers it.
Just building or testing?
Use a manual trigger. Every workflow can be run by hand from the editor - no setup needed.