Untimely

Use case

Schedule the request. Keep your endpoint focused on the work.

Your endpoint already knows how to run the job. Untimely handles when to call it. Create a recurring Webhook event, choose the hours it can start, and send the method, headers, and payload your handler expects. No scheduling loop to add to your service.

Run an n8n workflow at a random time

Add an n8n Webhook trigger node with HTTP Method POST and Respond set to Immediately, then publish the workflow and copy its Production URL. Replace https://your-n8n.example.com/webhook/<id> in the request below with that URL. If the node uses Header auth, add the matching key and value to Untimely’s webhook.headers.

Untimely sends the trigger; n8n runs the workflow. No polling or Wait-node loop is needed for this schedule. The example requests three triggers per seven-day interval, during 09:00–17:00 on eligible weekdays in America/Toronto.

Allow for the scheduling limits

The shortest interval is one day, with 1–5 triggers per interval and intervals up to 365 days. Windows use hours and minutes; the scheduler checks for due runs every five minutes, so delivery may be later than the selected time. This is not an every-40–90-minutes timer or a minimum-gap guarantee.

Connect an existing HTTP job

Use a Webhook event for a maintenance task, a content publisher, or a periodic check. Set it up in the dashboard or create it with one API request. Supported methods are GET, POST, PUT, PATCH, and DELETE, with up to 25 custom headers and a body up to 64 KB. GET requests do not accept bodies.

Say how often and within which hours

For three checks over seven days, set interval to 7 and frequency to 3. Choose the start and end of the allowed window and, if needed, eligible weekdays. Include an IANA timezone for local hours; omitting it uses UTC. Untimely selects the trigger times within those rules.

Check the delivery without digging through your server

Event history shows delivery results alongside the schedule. For API setup, reuse the same Idempotency-Key and request body when retrying event creation to avoid duplicates. Keep job completion tracking in your handler, especially when it starts background work.

API example

Create an API key in dashboard settings, replace the n8n URL, then send this request:

curl -sS "https://untimely.app/api/events" \
  -H "authorization: Bearer $UNTIMELY_API_KEY" \
  -H "content-type: application/json" \
  -H "idempotency-key: random-webhook-001" \
  -d '{
    "name": "Run n8n at random times",
    "scheduleType": "random",
    "interval": 7,
    "frequency": 3,
    "betweenTimeStart": "09:00",
    "betweenTimeEnd": "17:00",
    "timezone": "America/Toronto",
    "daysOfWeek": [1, 2, 3, 4, 5],
    "actionType": "WEBHOOK",
    "webhook": {
      "method": "POST",
      "url": "https://your-n8n.example.com/webhook/<id>"
    }
  }'

FAQ

Before you set it up

Is there a fixed-time option too?

Yes — set scheduleType to "deterministic" with a fixedTime and an IANA timezone.

Are windows timezone-aware?

Both schedule types support IANA timezones. A random window uses UTC if you omit timezone.

How do I authenticate?

Create an API key in dashboard settings and send it as a Bearer token.

Create your first event