Cron to Flow
Cron to Flow agents execute a flow on a schedule instead of waiting for an inbound HTTP request or an external event.
What they do
run the selected flow according to the cron expression in the agent's Schedule field
expose a Manual Run action in the agent UI for ad hoc execution
use flows built around
Event Start,Event End, andEvent Errornodes rather than HTTP entry points
Flow requirements
Cron to Flow agents use flows built around the event nodes. In practice, that means the selected flow should include:
at least one Event Start node
one or more Event End and/or Event Error nodes
This matches the same event-node requirement used for other event-driven agent types.
How they differ from long-running agents
Cron to Flow agents are configured around a schedule. In the current product UI, the schedule field replaces the parallel-instance scaling controls shown for HTTP and event-stream agents.
Schedule examples
0 * * * *runs at the start of every hour0 0 * * *runs once a day at midnight
Good fits
recurring data synchronization
hourly or daily rollups
scheduled cleanup and maintenance jobs
periodic notifications, exports, or follow-up tasks
Last updated
Was this helpful?