Scheduled Trigger Node - Time-Based Agentic Flow Automation in ConvyAI

Overview

The Scheduled Trigger node starts an Agentic Flow automatically according to a configured time schedule. It supports two configuration modes: a guided mode with visual controls for selecting recurrence units, and a custom (cron) mode for advanced scheduling using standard cron syntax. A natural-language hint displays the schedule interpretation in real time.

Positioning

The Scheduled Trigger node has no incoming connections and must be placed as the first node in the flow. Multiple Scheduled Trigger nodes can coexist in the same flow - each generates an independent schedule and can start separate runs of the same flow.

Configuration

Guided mode

Select the primary time unit and fill in the corresponding controls:

Time unit	Available controls
Minutes	Every N minutes (0–59)
Hours	Every N hours, at MM minutes (0–23, 0–59)
Days	Every N days, at HH:MM
Weeks	Day(s) of the week + time
Months	Day of the month (1–31) + time

The guided configuration generates a 5-field cron expression internally.

Custom (cron) mode

Enter a 5-field cron expression manually:

minute  hour  day-of-month  month  day-of-week

Field	Accepted values
minute	0–59
hour	0–23
day-of-month	1–31
month	1–12
day-of-week	0–7 (0 and 7 both represent Sunday)

Supported characters: *, -, ,, /

Example: */5 * * * * - every 5 minutes.

Natural-language hint

Below the configuration area, a real-time hint displays the plain-text interpretation of the current schedule (e.g., */5 * * * * → "Every 5 minutes"). The hint updates on every valid change without saving. If the expression is invalid, the hint shows an error message and saving the node is blocked.

Runtime behavior

• Each occurrence of the cron expression starts a new run of the flow.
• Runs are started within 59 seconds of the scheduled time, calculated against the tenant's configured timezone.
• No backfill: missed runs due to downtime or a disabled flow are not recovered. The scheduler resumes from the next future occurrence.
• If the flow is disabled, all associated schedules are suspended automatically.
• Multiple instances of the same flow can run simultaneously if schedules overlap.
• Runs started by a Scheduled Trigger are identifiable in the Monitoring page.

Output

The Scheduled Trigger does not expose a request payload. The following execution metadata is available to downstream nodes:

Key concepts

Term	Definition
Cron expression	A 5-field string that defines the schedule: minute hour day-of-month month day-of-week.
Guided mode	Visual interface for configuring the schedule without knowledge of cron syntax.
Backfill	Recovery of missed executions. The system does not implement backfill - skipped runs are never recovered.