Docs

Triggers

Choose how a workflow starts with Manually Run, Recurring Schedule, Listen for Webhook, or an app event.

Every workflow needs exactly one trigger. The trigger decides when a run starts. Built-in options live under Flow Control; app events sit under Apps.

This page explains the three Flow Control triggers. For how to place a trigger on the canvas, see Build on the canvas. For built-in steps after the trigger, see Flow Control.

Pick a trigger

On a new workflow, click Select a trigger... (or the + on the empty placeholder). Flow Control triggers appear at the top of the menu. App triggers are listed under Apps. Use Search to jump to a name.

1 Search. 2 Manually Run. 3 Recurring Schedule. 4 Listen for Webhook. App triggers follow under Apps.

Manually Run

Use Manually Run when you want to start a run yourself (or from another workflow or an agent). It is the simplest trigger while you design and test.

Click the node to open its settings. You can optionally add input fields so each run asks for values. Use Save & Test or Save when you are done.

1 Add optional input. 2 Save and Test. 3 Save.

Good for:

  • Learning the canvas and testing step by step
  • Workflows you start on demand from the builder or another process
  • Agent-requested runs when the trigger is available to agents

Recurring Schedule

Use Recurring Schedule when the workflow should run on a calendar (daily, weekly, and so on).

Open the node and set:

FieldPurpose
StartWhen the schedule begins (required)
RepeatsHow often it runs (appears after Start is set)

Save the trigger, turn Active on, and click Save in the header so the schedule can fire.

Set Start (required), then Save. After Start is set, choose how the schedule Repeats.

Listen for Webhook

Use Listen for Webhook when an external system should start the workflow with an HTTP request.

Open the node and set:

FieldPurpose
Unique Webhook URLThe URL for this workflow (copy it into the other system)
HTTP MethodPOST, PUT, or GET (must match what the caller sends)

Use Save & Listen or Save, then activate and save the workflow so Automate accepts requests.

1 Unique Webhook URL. 2 HTTP Method. Then Save or Save and Listen.

App triggers

Many connected apps also offer triggers (for example “new email” or “new file”). They appear under Apps in the same picker. You usually need a connection for that app before the trigger can run. See Integrations.

Next