Recurring runs
Daily, weekly, monthly, or a custom cadence — set the rhythm once and it repeats.
Daily analytics · weekdays 09:00
Mo
Tu
We
Th
Fr
Schedules
Set it, and it runs itself.
Put any workflow on a schedule — daily, weekly, or at a precise time — and your agent runs it on the clock, in the right time zone, every time.
Daily analyticstoday 09:00Pipeline reportMon 08:30Invoice chaseTue 10:30
Daily analyticstoday 09:00
Manual vs scheduled
Stop remembering.
Start scheduling.
Ad-hoc means you’re the scheduler — you have to be there to press go. Put the work on a schedule and the clock does it, on time, every time.
Manual / ad-hoc
Actionist Scheduleson the clock
Cadence
You have to remember to run it
Any cadence, set onceSix frequencies, minutely to yearly — interval 1–100
Timing
Whenever you get around to it
Fires on the minute±60 s execution precision
Time zones
You do the timezone (and DST) math
Timezone-awareIANA zones — daylight saving handled automatically
Setup
Cron syntax and config to look up
No cron syntaxA plain-English recurrence sentence
When it fails
A missed run just… doesn’t happen
Retries automaticallyUp to 3 retries, then logged with a reason
Visibility
No record of what ran
Full run historyEvery run, status, and transcript — 90 days
Cadence
Manual / ad-hocYou have to remember to run it
Actionist SchedulesAny cadence, set onceSix frequencies, minutely to yearly — interval 1–100
Timing
Manual / ad-hocWhenever you get around to it
Actionist SchedulesFires on the minute±60 s execution precision
Time zones
Manual / ad-hocYou do the timezone (and DST) math
Actionist SchedulesTimezone-awareIANA zones — daylight saving handled automatically
Setup
Manual / ad-hocCron syntax and config to look up
Actionist SchedulesNo cron syntaxA plain-English recurrence sentence
When it fails
Manual / ad-hocA missed run just… doesn’t happen
Actionist SchedulesRetries automaticallyUp to 3 retries, then logged with a reason
Visibility
Manual / ad-hocNo record of what ran
Actionist SchedulesFull run historyEvery run, status, and transcript — 90 days
How it works
Any cadence,
any timezone, on the clock.
Time-based triggers
Market open, business hours, end of day — pick the exact moment.
Todaytasks / hour
0810121416
Timezone-aware
Correct timing for global operations — daylight saving handled for you.
Runs at 09:00 in America/New_York
09:00 · New York 14:00 · London
Daylight saving handled automatically
Use cases
Set it once.
Then it just happens.
Your week, already handled.
Put each recurring job on the clock and your agents just run it — a morning digest, a Friday report, a month-end reconciliation — waiting for you every time.
Standup digest
Daily · 8:30 AM
Running…→ #engineering
Performance report
Weekly · Fri 5:00 PM
→ Home feed
Invoice reconciliation
Monthly · month-end
→ Telegram
Every run, start to finish.
When the clock fires, the agent runs the task and delivers the result — with a full transcript, and up to three automatic retries if anything fails.
Clock fires
09:00, on time
Agent runs
does the task
Result delivered
to your feed
Retries up to 3× on failure
A week of schedules
Every agent,
on its own schedule.
Recurring jobs across your whole team, all firing on the clock — while you get on with your day.
This week
Maya · MarketingDario · SalesPriya · SupportFelix · Finance
8 scheduled jobs · 4 agents · 24/79:00a
Daily analytics✓ 9:00
Maya · Marketing
1:00p
Queue health
Priya · Support
8A
9A
10A
11A
12P
1P
2P
3P
4P
5P
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Delivery
Fire once.
Deliver everywhere.
Each run drops its result where you want it — silently, on your home feed, in a conversation, or straight to Telegram or Slack.
DailyWeeklyPrecise time
09:00 · scheduled
Just run itHome feedConversationTelegramSlack
Cloud
Some schedules need to keep firing while your laptop is closed.
Move an agent to the hosted cloud runtime and its schedule keeps running — unattended, around the clock.
cloud runtime · laptop closed
onlineDaily analytics09:00
Pipeline reportMon 08:30
Invoice chaseTue 10:30
CSAT digestFri 16:00