One list
Every routine the company runs
Name, schedule, acting agent, last fire and next run, per Space. A failed fire shows on its row until someone deals with it.
AutomationsFree while the beta runs
Weekdays at eight.Without a reminder.
An Automation is a standing instruction, an agent and a trigger. Sales Analyst reads yesterday's orders every weekday morning and posts the digest as a message where the team already looks.
Starts on a schedule or a Task event. Every fire is a Run you can open.
What starts it
A time on the clock.Or a Task that changed.
The routine used to depend on someone remembering. Now the trigger is written down, with the agent that acts and the place the answer goes.
Schedule
Every day, every weekday, every week or every hour
Pick a preset or write a cron expression. The time is read in the timezone you choose, so eight means eight in Trnava.
Task event
When a Task changes status or gets a tag
Any status change or one status, any tag or one tag, inside the Automation's own Space. Changes that land within a minute arrive as one fire.
The agent's access, nothing more
Each fire runs as the agent you chose, with the permissions it has at that moment.
An answer with an address
Post to a channel the team reads. A scheduled Automation can also answer only you, in a private conversation.
Yours to switch off
Disable it, change the schedule or run it by hand. Each change is in the Automation's history.
Scheduled is a promise to try.You see when it could not.
A fire needs a Work Machine that is online and a provider with capacity left. On Wednesday the studio machine was off. The fire is on the Automation's page as did not run, with Retry beside it. Martin retried at 09:12.
Three ways a fire can go wrong.Each one says so.
No machine
Nothing picked the work up
If no Work Machine accepts the fire within ten minutes, it is marked as did not run, and the Automation's row in the list shows that its last fire failed.
Retry when ready
Usage limit
The AI provider said stop
When your AI plan reaches its limit, the Run shows that reason and the time the limit resets.
Retry after reset
The missed time
No surprise catch-up
A missed fire is never replayed on its own later in the day. You retry it, or the next one runs at its scheduled time.
Next run on schedule
Need numbers from your store or your invoicing?
Connect the service through MCP and choose which of its tools an agent may call.
Automations, answered.
What can start an Automation?
A schedule, or a Task event. Schedules run daily, on weekdays, weekly, hourly or on a custom cron expression in a timezone you pick. Task events are a status change and a tag being added, optionally narrowed to one status or one tag.
What happens if my Work Machine is offline at that time?
The fire waits up to ten minutes for a machine. If none takes it, the fire is recorded as did not run and you can retry it from the Automation's page. It is never silently dropped and never replayed without you.
Can an Automation do more than the agent behind it?
No. An Automation has no access of its own. If the instruction needs a step the agent may not take, the agent is refused there and can ask a person through an Action Request.
Who sees the result?
Whoever reads the channel you chose. For a scheduled Automation you can pick "Just for me", and the agent answers in a private conversation with you.
Can a burst of Task changes flood the team?
Matching events within a minute are collected into one fire, and one Automation fires at most 30 times an hour.
What does a typical first Automation look like?
A report: one bounded job, one source, one place for the answer. The reporting workflow shows it from the data to the follow-up Task.
Hand over one routine.
Pick the report someone writes by hand every week and give it a time. Free during the open beta.