Use case

Put the checks you keep postponing on a schedule.

A backup restore test is easy to leave until next week. So is reviewing a support ticket or checking a recent deploy. Put the checklist in an Untimely reminder and choose how often you want to see it. The prompt arrives within your working hours, with the next step already written out.

Choose the check before you choose the schedule

Write one concrete action: restore a test file, review one closed ticket, or verify one step in a process. Set three reminders per 30-day interval if a few checks each month would be useful. The timing varies; you decide what to inspect.

Put the next step where you will see it

For a personal checklist, create an Email event in the dashboard and write the instructions in the message. For a team workflow, use a Webhook action to call an endpoint that creates a ticket in your tracker. Start with one check on the free plan.

Keep a record of what you found

Use event history to check reminder delivery, then record the result of the actual inspection in your audit log or issue tracker. Delivery history confirms the prompt was sent; your findings show whether the work was completed.

API example

Prefer the API? Create an API key in dashboard settings, then adapt this request:

curl -sS "https://untimely.app/api/events" \
  -H "authorization: Bearer $UNTIMELY_API_KEY" \
  -H "content-type: application/json" \
  -H "idempotency-key: monthly-spot-checks-001" \
  -d '{
    "name": "Monthly random spot checks",
    "interval": 30,
    "frequency": 3,
    "betweenTimeStart": "14:00",
    "betweenTimeEnd": "22:00",
    "daysOfWeek": [1, 2, 3, 4, 5],
    "actionType": "EMAIL",
    "content": "Spot check: pick one item from the audit list and verify it end to end. Reply-all with what you found.",
    "contentType": "static"
  }'

FAQ

Before you set it up

Can different prompts go to different people?

Create one event per prompt or per owner — each event has its own window, action, and history.

Can the prompt itself vary?

On Pro, set contentType to "gpt" for generated email content. Use static text when the checklist must stay the same.

How many checks per cycle?

frequency supports 1–5 triggers per interval; interval runs up to 365 days.