Manual, Webhook, and Scheduled Workflows
Configure the resources that start a published workflow.
Choose the trigger in the builder, then save and publish the workflow. Trigger resources require a saved, published version. App-event triggers run when their matching event occurs and do not need a manual schedule or webhook endpoint.
Manual runs
For a manual trigger, select Run now in the trigger resources panel. This executes the published workflow and can perform real actions. Use Test workflow for simulation instead.
Open the resulting run and review its status, step outputs, and created or changed records.
Webhook endpoints
For a webhook trigger, use Generate webhook and copy the endpoint and newly displayed secret. Store the secret securely; it is shown when generated.
Send a POST to the copied endpoint with a JSON object and Content-Type: application/json. Supply the secret as Authorization: Bearer YOUR_SECRET or x-workflow-secret: YOUR_SECRET.
The workflow webhook is an incoming trigger. It is separate from outgoing webhook subscriptions.
If the request fails, check the endpoint, secret, published version, and JSON object body. A missing or invalid secret is rejected. Review the first successful run before enabling repeated requests.
Schedules
For a schedule trigger, choose Hourly, Daily at 9:00, or Weekdays at 9:00. The builder uses your browser's timezone when creating the schedule. Review the saved timezone, next run time, and Active or Paused status.
Check recurring actions for duplicate messages or records. A schedule starts the whole workflow; a Delay pauses a run that has already started.
Review execution
A successful trigger request is not proof that every action completed. Inspect run detail and any downstream record or message before retrying.