Skip to main content

Schedulers & Triggers

Control when and how workflows start execution.

Available Nodes


Start

Manually start a workflow with the Run button.

Use Cases

  • Testing workflows during development
  • On-demand execution
  • Entry point for manual processes
Every workflow needs at least one trigger node (Start, Cron Scheduler, a Webhook, or another event trigger) to begin execution.

Cron Scheduler

Run workflows on a recurring schedule. Instead of raw cron expressions, you pick a frequency and then set the matching interval or time-of-day fields. The Cron Scheduler is also a dual-purpose node — it can be connected to an AI Agent’s input-tools handle so agents can schedule delayed or recurring runs programmatically.

Parameters

select
default:"minutes"
How often the schedule fires: seconds, minutes, hours, days, weeks, months, or once. The other fields below appear based on the frequency you choose.
number
default:"30"
Seconds between fires (5-59). Shown when frequency is seconds.
number
default:"5"
Minutes between fires (1-59). Shown when frequency is minutes.
number
default:"1"
Hours between fires (1-23). Shown when frequency is hours.
select
default:"09:00"
Time of day (HH:MM). Shown when frequency is days.
select
default:"1"
Day of week for weekly schedules (0=Sunday … 6=Saturday). Shown when frequency is weeks.
select
default:"09:00"
Time of day for weekly schedules. Shown when frequency is weeks.
select
default:"1"
Day of month (1-28, or L for the last day). Shown when frequency is months.
select
default:"UTC"
IANA timezone identifier (UTC, America/New_York, America/Los_Angeles, Europe/London, Europe/Berlin, Asia/Tokyo, Asia/Kolkata).

Frequency Examples

Output

Example: Daily Report


Timer

Add a delay between nodes. The Timer is a dual-purpose node — it works both as a workflow delay node and as an AI Agent tool.

Parameters

number
default:"1"
Delay duration (1-86400).
select
default:"seconds"
Time unit: seconds, minutes, or hours.

Use Cases

  • Rate limiting API calls
  • Waiting for external processes
  • Scheduling sequential actions
  • AI Agent tool — agents can set timers programmatically when connected to input-tools

As a Workflow Node

As an AI Agent Tool

Connect the Timer to an agent’s input-tools handle. The agent can then invoke the timer to introduce delays during reasoning:
See AI Tools for the full tool schema and LLM interaction details.

Output


Python Executor

The Python Executor moved to its own page alongside the other code nodes — see Code Executors. It pairs naturally with schedulers: a Cron Scheduler firing into a Python Executor is the classic zero-credential automation.

Combining Schedulers

Schedule with Delay

Multiple Schedules

Deploy workflows with different schedules:

Workflow States

After deployment, trigger nodes show their state:

Tips

The Cron Scheduler uses a frequency dropdown — pick minutes/hours/days/weeks/months/once and fill in the matching interval or time-of-day field. No raw cron expression is needed.
Use Python Executor for conditional logic instead of multiple workflow branches.
Add Timer nodes when calling rate-limited APIs repeatedly.
Cron schedules are in UTC by default. Set timezone if needed.

Troubleshooting

  • Verify workflow is deployed (not just saved)
  • Check that the frequency and its interval/time fields are set
  • Ensure timezone is correct
  • Check server logs for errors
  • Check for syntax errors
  • Verify input_data has expected fields
  • Use try/except for error handling
  • Print debug info with print() (shows in logs)
  • Ensure the duration is at least 1 (max 86400)
  • Check the unit (seconds vs minutes vs hours)
  • Verify node is connected properly

Webhooks

Trigger workflows via HTTP

WhatsApp

Message-triggered workflows