Connic
Connectors

Cron Scheduler

Run your agents on a recurring schedule using standard cron expressions. Perfect for automated reports, monitoring, and periodic tasks.

Inbound Mode

Cron connectors operate in inbound mode only. They trigger your agents on a schedule and immediately queue the run. Agents process in the background.

How Cron Works

Cron connectors trigger your linked agents automatically based on a schedule you define. When the scheduled time arrives, Connic dispatches a run to all agents linked to the connector. Best for daily/weekly reports, periodic data syncing, scheduled monitoring, and automated notifications.

Schedule

The schedule uses standard cron expression format with 5 fields:

┌───────────── minute (0 - 59)
│ ┌───────────── hour (0 - 23)
│ │ ┌───────────── day of month (1 - 31)
│ │ │ ┌───────────── month (1 - 12)
│ │ │ │ ┌───────────── day of week (0 - 6) (Sunday = 0)
│ │ │ │ │
* * * * *

Common Schedules

0 * * * *Every hour
0 0 * * *Every day at midnight
0 9 * * 1-5Weekdays at 9 AM
0 0 * * 0Every Sunday at midnight
*/15 * * * *Every 15 minutes
0 0 1 * *First of every month

More Examples

bash
# Every day at midnight
0 0 * * *

# Every hour
0 * * * *

# Every Monday at 9 AM
0 9 * * 1

# Every weekday at 9 AM
0 9 * * 1-5

# Every 15 minutes
*/15 * * * *

# First day of every month at midnight
0 0 1 * *

Prompt (Optional)

You can optionally configure a prompt that will be included in the payload sent to your agent on each scheduled run. For example: "Generate the daily sales report for yesterday".

Payload Format

json
{
  "trigger": "cron",
  "schedule": "0 9 * * 1-5",
  "triggered_at": "2024-01-15T09:00:00.000Z",
  "prompt": "Generate the daily report"
}

Includes trigger ("cron"), schedule,triggered_at (ISO timestamp), and your configured prompt.

Timezone

All cron schedules are evaluated in UTC timezone. To run at 9 AM Eastern Time, set the schedule to run at 14:00 UTC (during standard time).