Triggers and schedules

How a workflow starts is set in the Triggers section of the start node's panel on the canvas. The summary on the canvas reads like "Manual · 2 schedules · 1 webhook".

Manual

Always available. Use the Run button at the top of the workflow page, or ask for a run in chat. If the workflow has inputs, the Run workflow panel asks for them first and shows a Cost estimate and your balance. Run uses the deployed version, so deploy your changes first.

For a draft that you are still building, use Test run instead. See Build a workflow.

Schedules

A schedule runs the workflow automatically and always starts the latest deployed version. Schedules are available on Business and Enterprise; on Free the action is locked.

1. Deploy the workflow first

   A scheduled trigger cannot be created until the workflow has an active deployment.

2. Add a schedule

   In the Triggers section, choose Add schedule (New scheduled trigger) and give it a Name, for example "Daily report".

3. Set when

   Choose a preset such as Daily at 09:00 or Every Monday 09:00, or a custom cron expression, and the timezone.

4. Add input (optional)

   Under Input (optional, JSON) enter values that are passed into the workflow on every run.

5. Create the trigger

   Choose Create trigger.

You can also schedule a workflow from Schedule in the same way as an agent: choose Workflow as what to run. See Schedules and triggers for the dialog.

Webhooks

A webhook lets another system start the workflow with a signed request.

1. Under Webhooks, choose Add webhook.
2. Enter a name and an optional description, then Create webhook.
3. Copy the Webhook URL and the Signing secret. The secret is shown only once.

The calling system sends a timestamp header and a signature header, computed with the secret. The exact header names and the formula are shown on the page when you create the webhook. Requests that are too old are refused.

Forms and connected apps

The Triggers section of the start node, and the global Triggers page (find it with the search at the top of the screen), also let you create:

• A Form trigger: a public form whose submissions start the workflow. You design the fields, the submit button and the success message.
• An App trigger: starts the workflow when something new happens in a connected app, currently Gmail or Jira. You choose the event and the connection.

All triggers are listed on the Triggers page, with a type label and View fire history to see when each one fired.

Related

• Workflow runs
• Triggers for agents