Skip to main content
connic

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.
Schedules
UTC
ExpressionRuns
*/15 * * * *Every 15 minutes
0 * * * *Every hour, on the hour
0 9 * * 1-5Weekdays at 09:00
0 0 * * 0Sundays at midnight
0 0 1 * *First day of each month at midnight

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.
context["payload"]
{
  "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.

connectors/daily-sales-report.yaml
type: cron
name: Daily sales report
config:
  schedule: "0 6 * * *"
  prompt: Write yesterday's sales report.
agents:
  - sales-reporter
environments:
  Production: {}
create: connectors/daily-sales-report.yaml (cron)

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.
connectors/sales-report-delivery.yaml
type: webhook
mode: outbound
name: Sales report delivery
config:
  outbound_url: ${REPORTS_URL}
agents:
  - name: sales-reporter
    outbound:
      usage: automatic
      source: [daily-sales-report]
outbound-payload.json
{
  "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.

Every day at 06:00
Cron Scheduler
sales-reporter
Report by email
payload.json
{
  "trigger": "cron",
  "schedule": "0 6 * * *",
  "triggered_at": "2026-10-13T06:00:00+00:00",
  "prompt": "Write yesterday's sales report."
}
output.json
{
  "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.

Every hour
Cron Scheduler
service-checker
Alert in Slack
payload.json
{
  "trigger": "cron",
  "schedule": "0 * * * *",
  "triggered_at": "2026-10-13T09:00:00+00:00",
  "prompt": "Check checkout and login. Alert on failures."
}
connector-payload.json
{
  "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.

Mondays at 09:00
Cron Scheduler
compliance-scanner
Findings to your API
payload.json
{
  "trigger": "cron",
  "schedule": "0 9 * * 1",
  "triggered_at": "2026-10-12T09:00:00+00:00",
  "prompt": "Check new regulatory updates against our policies."
}
outbound-payload.json
{
  "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.

Every night at 02:00
Cron Scheduler
crm-cleaner
Contacts merged in your CRM
payload.json
{
  "trigger": "cron",
  "schedule": "0 2 * * *",
  "triggered_at": "2026-10-13T02:00:00+00:00",
  "prompt": "Merge duplicate contacts created yesterday."
}

Cron Scheduler FAQ

Add a Cron Scheduler connector to the agent, enter a five-field cron expression and, if you like, a prompt. When the schedule fires, connic starts a run for every linked agent. You can also declare the connector in connectors/ with type: cron. To see how schedules fit next to event triggers, read about common connector patterns.

Every schedule runs in 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.

No runs start while the connector is paused. Schedule times that pass during the pause are not made up after you resume.

Link an outbound connector to the same agent. An automatic outbound connector sends after every completed run, scheduled ones included, and you can limit it to runs the cron connector started. Every run also shows its output and traces in Agent Runs.