Cron Scheduler
Pick a cron string, point it at an agent. Daily digests, hourly health checks, weekly audits: runs are logged, retries are automatic and configurable per agent, and you don't host the scheduler.
Overview
The cron connector runs agents on a standard five-field cron expression. When the schedule fires, Connic dispatches a run to every agent linked to the connector, with a payload carrying the schedule, the trigger timestamp, and an optional prompt you configure once. All schedules are evaluated in UTC.
There is no scheduler to host and no box whose crontab you have to remember exists. Each tick queues a run like any other trigger, so scheduled work goes through the same pipeline as event-driven work instead of living in a script on a forgotten server.
How it works
Create the connector
Open your agent, click Add inbound connector in the Connector Flow, and select Cron Scheduler. Cron connectors are inbound only: they trigger runs on a schedule and the agent processes in the background.
Set the schedule
Enter a standard five-field cron expression, like 0 9 * * 1-5 for weekdays at 9 AM. Schedules are evaluated in UTC, so convert local times before creating the connector.
Optionally set a prompt and create
The prompt is included in the payload on every scheduled run, for example 'Generate the daily sales report for yesterday'. When the schedule fires, Connic dispatches a run to all agents linked to the connector.
What you can build
Patterns teams ship in production. No queues, workers, or schedulers to run.
Every morning at 7am
0 7 * * *Agent picks the three articles each user is most likely to read, writes a subject line in their voice, and ships the send before they pour coffee.
Every morning at 7am
0 7 * * *Agent picks the three articles each user is most likely to read, writes a subject line in their voice, and ships the send before they pour coffee.
Cron expressions and timezones
Schedules use the standard five-field format: minute, hour, day of month, month, day of week. 0 * * * * runs every hour, */15 * * * * every 15 minutes, 0 0 1 * * on the first of every month.
Every schedule is evaluated in UTC. To run at 9 AM Eastern Time, set the schedule for 14:00 UTC during standard time. Doing the conversion once at setup beats debugging a report that shifts by an hour twice a year.
What the agent receives
Each trigger sends a payload with trigger set to "cron", the schedule expression, a triggered_at ISO timestamp, and your configured prompt. The agent can key off the timestamp for date-dependent work like yesterday's report or this week's digest.
Every scheduled tick is a normal agent run: it appears in run history with full traces, token and cost tracking, and the same guardrails and approval rules as any other trigger, so a quiet 3 AM job is as inspectable as a live one. See the payload format and more schedule examples in the cron docs.
Information
- Publisher
- By Connic
- Category
- Connectors
- Modes
- Inbound
- Documentation
- Cron Scheduler docs
Frequently Asked Questions
How do I run an AI agent on a schedule?
What timezone do cron schedules use?
Can I tell the agent what to do on each run?
triggered_at timestamp. The agent reads it as its instruction for that run.Bring the event source, payload shape, result destination, and any private-network or approval requirements. We will map Cron Scheduler to the right Connic connector mode, deployment path, and observability setup.
Talk to Sales