Skip to Content
Docs are being rebuilt — start at Introduction → How it works.

Triggers

Trigger nodes decide how a workflow starts. The current builder exposes manual, schedule, webhook, and app-event triggers, plus an End node for explicit completion.

What you can do here

  • Start a workflow manually while testing.
  • Run a workflow on a time schedule.
  • Start a workflow from an incoming webhook.
  • Start a workflow from a connected app event.
  • Mark the end of a workflow path.
New Workflow builder showing the Trigger category with Manual Start, Schedule Trigger, Webhook Trigger, App Trigger, and End

Trigger nodes

NodeUse it forMain configuration
Manual StartOn-demand testing and workflows that should only run when a user starts them.Optional node label only.
Schedule TriggerTime-based workflow runs.Timezone, Time, Date, recurring toggle, end behavior, end date, and number of occurrences.
Webhook TriggerWorkflows started by an external HTTP request.Webhook URL, HTTP Method, Authentication, credentials when required, and Response Format.
App TriggerWorkflows started by events from a connected app.App, Connection, Trigger, and trigger-specific parameters.
EndExplicitly stop a path.Optional node label only.

Schedule Trigger fields

FieldOptionsWhat it controls
TimezoneTimezone pickerThe timezone used to calculate scheduled runs.
TimeTime inputThe local run time.
DateDate pickerThe first or one-time run date.
RecurringToggleTurns a one-time schedule into a recurring schedule.
EndsNever, On Date, AfterWhether the schedule continues, stops on a date, or stops after a number of runs.
End DateDate pickerThe final date when On Date is selected.
Number of OccurrencesNumber inputThe maximum run count when After is selected.

Webhook Trigger fields

FieldOptionsWhat it controls
Webhook URLGenerated URL with copy actionThe endpoint external systems call to start the workflow.
HTTP MethodGET, POST, PUT, DELETEWhich HTTP method the endpoint accepts.
AuthenticationNone, Basic Auth, Bearer Token, API Key, HMAC SignatureHow callers prove they are allowed to start the workflow.
CredentialsVaries by authentication typeStores the key, token, username/password, or signing secret required by the selected method.
Response FormatJSON, XML, Plain TextThe response format returned to the caller.

App Trigger fields

FieldWhat it controls
AppThe connected application that will emit the event.
ConnectionThe workspace connection used for that app.
Create New ConnectionOpens the connection flow when no usable connection exists.
TriggerThe event type from the selected app.
ParametersEvent-specific settings required by the selected trigger.

Trigger selection checklist

NeedUse
Test a workflow from the builder or Flows listManual Start
Run a report every morningSchedule Trigger
Let another system start the workflowWebhook Trigger
React to an event from a connected appApp Trigger
Stop a branch after its final actionEnd