Cron Scheduler
Run an agent on any cron expression. connic hosts the scheduler and starts every linked agent with the schedule, the trigger time and your prompt.
- Modes
- Inbound
- Set up in
- Dashboard or connectors/*.yaml
- Documentation
- Cron Scheduler docs
- Publisher
- By connic
Schedule an agent with a cron expression
Enter a standard five-field expression. When it matches, connic starts a run for every linked agent, and you don't host a scheduler or a worker.
- Five fields
- Minute, hour, day of month, month and day of week, in the same format as a crontab.
- Always UTC
- To run at 9 AM Eastern Time, schedule 14:00 UTC during standard time, and adjust the expression when daylight saving time starts or ends.
- Paused schedules
- While the connector is paused, no runs start. Schedule times that pass during the pause are not made up.
Tell the agent what each run is for
Every run gets a small payload with the schedule, the time it fired and the prompt you set on the connector.
- Your prompt
- Write the instruction once, such as Write yesterday's sales report. It goes out with every run and is left out when the field is empty.
- The trigger time
- triggered_at is the minute the schedule fired, in UTC. Use it for date-bound work like yesterday's report or this week's digest.
- One run per agent
- Link several agents to the connector, and each one gets its own run from the same tick.
{
"trigger": "cron",
"schedule": "0 6 * * *",
"triggered_at": "2026-10-13T06:00:00+00:00",
"prompt": "Write yesterday's sales report."
}Keep the schedule next to your agents
Declare it as a YAML file in connectors/. Each deploy creates or updates it for its environment, and a rollback restores the schedule that deployment had. List only the environments that should run it.
type: cron
name: Daily sales report
config:
schedule: "0 6 * * *"
prompt: Write yesterday's sales report.
agents:
- sales-reporter
environments:
Production: {}Send each run's result onward
Link an outbound connector to the same agent, and the output of every scheduled run goes to your API or your team's inbox.
- Automatic delivery
- An automatic outbound connector sends after every completed run. Set source to the cron connector to send only the runs this schedule started.
- Only when it matters
- Linked as an agent tool, the outbound connector lets the model decide whether to send, for example only when a check fails.
- Every run in Agent Runs
- Each scheduled run shows its output, traces and token usage in Agent Runs, like any other run.
type: webhook
mode: outbound
name: Sales report delivery
config:
outbound_url: ${REPORTS_URL}
agents:
- name: sales-reporter
outbound:
usage: automatic
source: [daily-sales-report]{
"run_id": "550e8400-e29b-41d4-a716-446655440000",
"agent_name": "sales-reporter",
"status": "completed",
"output": "October 12: 412 orders, EUR 38,920, up 6% on last week.",
"error": null,
"started_at": "2026-10-13T06:00:01Z",
"ended_at": "2026-10-13T06:00:09Z",
"token_usage": {
"input_tokens": 2140,
"output_tokens": 186,
"thinking_tokens": 0,
"cached_input_tokens": 0,
"total_tokens": 2326
}
}Where a schedule fits
Pick a setup to see when it runs, what the agent receives and where the result goes.
Every morning at 06:00 the agent sums up yesterday's sales and sends the report by email.
{
"trigger": "cron",
"schedule": "0 6 * * *",
"triggered_at": "2026-10-13T06:00:00+00:00",
"prompt": "Write yesterday's sales report."
}{
"to": "sales-team@example.com",
"subject": "Sales report for October 12",
"body": "412 orders and EUR 38,920 in revenue, up 6% on last week."
}Every hour the agent checks your endpoints with its tools and posts to Slack only when something fails.
{
"trigger": "cron",
"schedule": "0 * * * *",
"triggered_at": "2026-10-13T09:00:00+00:00",
"prompt": "Check checkout and login. Alert on failures."
}{
"text": "Checkout returned 503 in 3 of 5 checks since 08:00 UTC.",
"channel_id": "C01234567"
}On Mondays at 09:00 the agent checks new regulatory updates against your policies, and an outbound webhook sends the findings to your API.
{
"trigger": "cron",
"schedule": "0 9 * * 1",
"triggered_at": "2026-10-12T09:00:00+00:00",
"prompt": "Check new regulatory updates against our policies."
}{
"run_id": "550e8400-e29b-41d4-a716-446655440000",
"agent_name": "compliance-scanner",
"status": "completed",
"output": "2 findings: retention policy outdated, one DPA missing.",
"error": null,
"started_at": "2026-10-12T09:00:01Z",
"ended_at": "2026-10-12T09:02:44Z",
"token_usage": {
"input_tokens": 2140,
"output_tokens": 186,
"thinking_tokens": 0,
"cached_input_tokens": 0,
"total_tokens": 2326
}
}Every night at 02:00 the agent merges duplicate contacts from the day before through its tools.
{
"trigger": "cron",
"schedule": "0 2 * * *",
"triggered_at": "2026-10-13T02:00:00+00:00",
"prompt": "Merge duplicate contacts created yesterday."
}Cron Scheduler FAQ
More connectors
Apache Kafka
Consume topics to trigger agents and produce results back to topics under the source message key.
Inbound · Outbound
AWS SQS
Drain SQS queues with an agent. Each message is deleted once its runs complete, and failed ones return after the visibility timeout.
Inbound · Outbound
MQTT
Subscribe to MQTT 5 topics to trigger agents from devices and machines, and publish results back to a topic.
Inbound · Outbound
Outlook (Microsoft 365)
Run an agent on new email in a Microsoft 365 mailbox and reply in the same thread. connic signs in with your own Entra ID app. Attachments included.
Inbound · Outbound
Pipedrive
Run an agent when deals, leads, people or organizations are created, updated or deleted in Pipedrive. It adds its result as a note to the record.
Inbound · Outbound
SIP Voice
Answer and place calls with a voice agent on any phone system or provider that supports SIP. Transfer callers and queue them while the agent is busy.
Sync · Outbound