Untimely

Use case

Give your agent a recurring job. Leave the wake-up time open.

To schedule an AI agent at random times, create an Untimely Webhook event with its trigger URL, an allowed time window, and 1–5 runs per interval. The request below schedules two triggers per one-day interval on eligible weekdays, between 13:00 and 21:00 in America/Toronto. Untimely sends the trigger; your endpoint runs the agent, with no scheduler to maintain.

API example

Create an API key in dashboard settings, then adapt this request to your endpoint:

curl -sS "https://untimely.app/api/events" \
  -H "authorization: Bearer $UNTIMELY_API_KEY" \
  -H "content-type: application/json" \
  -H "idempotency-key: agent-random-heartbeat-001" \
  -d '{
    "name": "Agent heartbeat at random times",
    "scheduleType": "random",
    "interval": 1,
    "frequency": 2,
    "betweenTimeStart": "13:00",
    "betweenTimeEnd": "21:00",
    "timezone": "America/Toronto",
    "daysOfWeek": [1, 2, 3, 4, 5],
    "actionType": "WEBHOOK",
    "webhook": {
      "method": "POST",
      "url": "https://agent.example.com/run",
      "headers": [{"key": "x-api-key", "value": "your-agent-key"}, {"key": "Content-Type", "value": "application/json"}],
      "body": "{\"task\": \"heartbeat\"}"
    }
  }'

Use a window when the exact minute adds nothing

A feed check can happen sometime in the afternoon. An occasional reflection prompt can arrive during working hours. A random schedule gives these jobs recurring starts at varied times. Choose a fixed schedule when another process needs the result at a known hour.

Set its schedule once

Create a Webhook event and choose the interval in days, up to five triggers per interval, and the allowed hours. Restrict weekdays if needed. Add an IANA timezone for local hours; API requests use UTC when you leave it out. The example above requests two triggers per one-day interval on eligible weekdays.

Connect the agent you already run

Point the request at a public endpoint that starts your agent, and include its authentication header and task payload. You can create the event in the dashboard or through the API. Send an Idempotency-Key when creating it through the API so retrying the same setup request does not create a second event.

FAQ

Before you set it up

How random is the timing?

Untimely chooses trigger times within your schedule rules. Times can repeat. Run history shows delivery results; it does not verify that the agent completed its task.

Can the endpoint be private?

The URL must be a public HTTP or HTTPS endpoint. Authenticate it with a header — the webhook config supports custom headers.

What plans does this need?

The free tier includes 3 events; Pro removes the cap.

Create your first event