Schedules

Recurring work that runs without you.

Set a cadence once. Every week, every client gets an audit. Every day, new content enters the queue — no manual triggers, no forgotten weeks.

Request Access
Schedules
SchedulesRecurring entity automation
4TOTAL
3ACTIVE
1PAUSED
seo analystswiftlatch-garagedemo-law✓ 2h ago
Every Mon at 09:00 UTC· next in 4d
last 10
RUN HISTORY
✓ completedJun 23 · 09:021m 48s↗ thread
✗ failedJun 16 · 09:01timeout↗ thread
✓ completedJun 9 · 09:032m 12s↗ thread
content pipelineswiftlatch-garage✓ 6h ago
Every day at 07:00 UTC· next in 6h 23m

Set-and-forget cadence

Hourly, daily, weekly, monthly, or custom cron — built with a visual builder that speaks human ("Runs every Monday at 09:00").

Cross-site sweeps

One schedule can cover every client at once. Weekly audits for ten sites is one schedule, not ten.

Full audit trail

Every run creates a complete chat thread — what the entity found, what it did, what it delivered. Jump from any run straight into the conversation.

Auto-protection

Three consecutive failures and the schedule disables itself, flagged for your review. No silent error loops burning resources.

On-demand trigger

Any schedule fires instantly with one click when you can’t wait for the next slot. Same entity, same instructions, right now.

Health at a glance

Each schedule shows its last ten runs as a health strip — greens, reds, and running states visible without opening anything.

Set it once. Forget it forever.

Weekly sweeps across your roster, from week one.

Request Access
FAQ

Straight answers

What happens if a scheduled run fails?

The failure is logged with its error, visible in the run history. After three consecutive failures the schedule auto-disables and gets flagged, so a broken credential never burns quietly for weeks.

Can one schedule handle all my clients?

Yes — schedules accept multiple sites. A "weekly GSC report" schedule with ten sites attached generates and delivers ten client reports every Monday.

Can I see exactly what a scheduled run did?

Every run links to its full chat thread: each tool call, each result, each entity involved. The audit trail is the same whether you triggered it or the cron did.

What timezone do schedules use?

UTC, displayed alongside a humanized description so there’s no ambiguity about when the next run fires.

Doesn’t scheduling runs across every client burn tokens?

No — the data work in a scheduled run happens in plain code, and the entity only reads computed results. That’s what makes a weekly sweep across a 60-client roster affordable, instead of a token bill you watch all month.

Request Access

Stop Prompting.
Start Orchestrating.

Tell us about your operation. We'll walk you through the platform, agree on pricing, and hand you the keys to your own dedicated instance.

Please enter your name.
Please enter a valid work email.