Automations · Nodes · trigger
Schedule
trigger.schedule · trigger
Cron / daily schedule.
When to use
- Use when you need: Cron / daily schedule.
Configuration
| Field | Required | Notes |
|---|---|---|
| preset | no | Schedule preset (e.g. daily) |
| timezone | no | IANA timezone for the schedule |
Inputs
Starts the run. Payload comes from the event, Manual / sample test, Listen capture, or pinned Input.
Outputs
Node result fields are available to downstream expressions. Check the Output tab after Execute or a full run.
Execute step (editor)
| Eligible? | Notes |
|---|---|
| Hidden | Event-driven — use Test run, Listen, or Input from a prior execution. |
See Test, Execute, debug, listen and limitations.
Common errors
| Symptom | Cause | Fix |
|---|---|---|
| Live event did not run | Draft unpublished or automation inactive | Publish changes and keep automation active. |
| No matching trigger | Account/keyword filter mismatch | Widen filters or confirm the event account. |
Example
Add this trigger → connect an action (e.g. send text or Slack) → Test with sample data or Listen → Publish when ready.