Event triggers
The Collabase plugs offer an event trigger for most apps. The trigger starts a run when the event happens, and the run receives the data of the event. A run starts only for objects that the workspace’s service account may see, so a flow never reacts to something it could not open.
The plug reference lists every trigger with the data it hands over. A flow never starts from an event that one of its own runs caused.
Webhook
Webhook received starts a run when another system calls the flow’s webhook address. The address is on the Trigger tab. You can require a login, accept files and test the call. Webhooks explains all of it.Schedule
On a schedule starts a run at a fixed interval, from every minute to every week. Choose an amount and a unit. A flow that is switched off does not run on its schedule, and a schedule picks up again when the flow is switched on. For fixed times, enter a Cron pattern instead of an interval, with five fields: minute, hour, day of the month, month and weekday. Set the Time zone (for exampleEurope/Zurich, which is the default) so the times follow daylight saving.
A pattern that cannot be read, an unknown time zone or a pattern that fires more than once a minute blocks publishing and names the field. When a cron pattern is set, the interval is ignored.
Called by another flow
Called by another flow starts a flow when another flow of the same Space runs the Run another flow step. The data the first flow passes becomes the trigger data. Use it to split a long flow into parts that several flows share. The called flow must be published and switched on.Another flow ended
Two triggers react to the production runs of the other flows in the same Space. Test runs do not start them.Chat message
Chat message received starts a run for each message that a visitor sends on the flow’s chat page. The Reply in the chat step answers the visitor.Triggers of other plugs
Installed core and community plugs bring their own triggers. They come in three kinds:
Plug triggers run in the sandbox. A flow with a plug trigger needs the sandbox to be available. Republishing the flow runs the trigger’s enable step again. Switch a flow off before you delete it, so that the other system forgets the address.
A poll starts runs for up to 5,000 new items. Items beyond that are skipped and the flow shows a trigger error that says how many. Items with identical content that arrive within 30 seconds start one run.
App webhooks
Some plugs deliver the events of an app, for example a chat app, to one address of your instance:<app> is the short name of the plug. The Trigger tab shows the full address with a copy button. Enter it in the app as the place it sends its events to. Then create a variable in the Space named APP_EVENT_SECRET_<APP> in capital letters, for example APP_EVENT_SECRET_SLACK, that holds the signing key of the app. The tab names the variable too. The trigger checks every event against it. A flow whose variable is missing receives no event and shows a trigger error that names the variable.
The address answers with what the app expects, such as an address check, whatever the flows do. A call that fails the signature check starts no run.
Test a trigger
A trigger shows sample data until a real event has happened. The data picker and Test flow use it. Under the trigger you can:
A plug trigger that has no way to deliver examples has nothing to load, and the page says so.