Skip to content

Input ​

An input says what starts a flow: a schedule.

Syntax ​

text
id[/"Label"/]@{ trigger: "schedule", cron: "…" }
id["Label"]@{ shape: input, trigger: "schedule", at: "…" }

Settings ​

SettingRequiredValueExample
triggeryes"schedule"trigger: "schedule"
crona schedule needs cron or at, not bothtext in crontab formatcron: "0 9 * * 1-5"
ata schedule needs cron or at, not botha date and 24-hour time, written YYYY-MM-DDTHH:MMat: "2026-12-24T09:00"
timezonenoa time zone nametimezone: "Europe/Madrid"

cron repeats and at runs once. Both are read in timezone, which is UTC when you leave it out. Triggers covers the schedule trigger and the cron format in detail.

Where it can go ​

An input sits at the top level of the workflow and holds nothing.

ArrowIn fromOut to
Arrow (-->)β€”flow
Dotted link (-.-)β€”β€”

An input can start any flow, even one inside another flow. One input can start several flows, and one flow can have several inputs.

Rules ​

Example ​

Code:
mermaid
agentflow TB
  weekday[/"Weekdays at 09:00"/]@{ trigger: "schedule", cron: "0 9 * * 1-5", timezone: "Europe/Madrid" }
  launch["Launch day"]@{ shape: input, trigger: "schedule", at: "2026-12-24T09:00" }

  flow triage["Issue triage"]
    read["Read issues"]@{ instruction: "Summarise every open issue." }
  end

  flow announce["Announce"]
    post["Post"]@{ instruction: "Post the launch announcement." }
  end

  weekday --> triage
  launch --> announce
Ctrl + Enter|

Common mistake ​

An arrow from an input straight to a task.

Code:
mermaid
agentflow TB
  weekday[/"Weekdays at 09:00"/]@{ trigger: "schedule", cron: "0 9 * * 1-5" }

  flow triage["Issue triage"]
    read["Read issues"]@{ instruction: "Summarise every open issue." }
  end

  weekday --> read
Ctrl + Enter|

Input "weekday" can only start a flow, but "read" is a task. Point the arrow at a flow instead.

Opens in mermaid.ai