Automation triggers

An automation can have multiple configured triggers. Manual execution is a separate action for testing or intentional one-off runs.

Scheduled

Choose Add Trigger → Scheduled. Configure the cron expression and timezone, then inspect the schedule shown by the form. The timezone is part of the schedule: do not assume UTC or the browser’s timezone. Check behavior near daylight-saving changes for local-time schedules.

Entity Events

Choose Entity Events, select the entities, and choose create, update, or delete events. Keep the selection narrow. An automation that writes back to its trigger entities needs loop protection and instructions that avoid unnecessary updates.

Webhook Triggered

Choose Webhook Triggered and use the generated incoming URL and configured secret in the calling integration. Treat the URL’s token and secret as credentials. Inspect the run input to confirm the intended payload arrived; do not expose them in logs or screenshots.

Incoming automation webhooks start AI work. Outgoing Dashboard webhooks notify another service about data changes. They are opposite directions and have separate setup.

Test before enabling

Run the task manually, verify its output and authority, then test one configured event or schedule in a development project. Check runs for failure, skipped, or awaiting-approval states. Enabling a trigger does not guarantee every execution will complete: credits, project state, permissions, and downstream tools still matter.