> For the complete documentation index, see [llms.txt](https://docs.contextual.io/documentation-and-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.contextual.io/documentation-and-resources/components-and-data/agents/types-of-agents/cron-to-flow.md).

# 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`, and `Event Error` nodes 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](/documentation-and-resources/components-and-data/flows/node-reference/event/event-start.md) node
* one or more [Event End](/documentation-and-resources/components-and-data/flows/node-reference/event/event-end.md) and/or [Event Error](/documentation-and-resources/components-and-data/flows/node-reference/event/event-error.md) 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 hour
* `0 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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.contextual.io/documentation-and-resources/components-and-data/agents/types-of-agents/cron-to-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.