ACT automations
An ACT automation runs work that repeats, the same way every time. You never build it by hand. You describe it to Boosty or an agent, and the agent writes it as code, tests it on your data and switches it on once you confirm. Every run is recorded, so you always see what ran and what came out.
It is the right kind for moving data between apps, scoring or tagging records, keeping data in shape and reports that follow a fixed recipe. It handles hundreds or thousands of records without the agent reading each one. For work that needs judgement every run, your agent builds an agent automation instead.
What can I automate?
- Reacting to your data. "When a lead is created, score it and post the hot ones to Slack."
- Reports on a schedule. "Every weekday at 7:00, send me yesterday's orders by country."
- Keeping data in shape. "Every night, fill in missing product categories."
- Reacting to other apps. "When our e-shop sends an order, add the customer to Contacts."
- Syncing with a service. "Every hour, copy new Stripe payments into the Payments module."
How do I build one?
Tell Boosty or an agent in Chat: when it runs, what it works with and what it does with the result. The agent builds it, tests it and asks you to confirm before it goes live. See Build with an agent.
Who can build them?
- An agent whose Automations access is Allowed. An admin sets it in Connections and security. The agent works only on the ACT automations it built itself.
- An admin from their own AI tool, through Connect AI (MCP), signed in with OAuth or with a token that has All permissions.
An ACT automation runs with the access of whoever built it. One that an agent built reaches only the data and modules the agent may use.
Where do I find them?
Click Automations in the left rail, then the ACT automations tab. Admins see the list. Each row shows the Automation with the one-sentence summary the agent wrote, When it runs, and its State: Active, Paused, or Needs a look when the last run failed. The tab says how many need a look. ACT automations belong to your whole system, not to one agent, so the list shows them with the scope on All agents.
What does an automation's page show?
Click an automation. The page shows:
| Part | What it says |
|---|---|
| Name and summary | What the automation does, in the agent's words, its number and when it last changed. |
| Runs as | Workspace: it belongs to your system, not to one agent. |
| When | Its triggers. A webhook that starts it is listed under it, as a link. |
| Status | Its state, and when it last ran. |
| Runs | Every run with its result. See Runs. |
| Code | The code it runs, with line numbers. Copy copies all of it. |
Two buttons sit at the top:
- Pause stops the automation. AgentOS asks you to confirm, because scheduled runs are skipped until you click Resume.
- Edit with Boosty opens the chat with "Change the ACT automation … so that" in the message box. When the last run failed, the button is Fix with Boosty, and the message asks for the cause and a fix.
To delete an automation, ask in Chat: "Delete the ACT automation Score new leads."
What does an ACT automation cost?
ACT automations run on the ACT Operations of your plan, not on the AI wallet:
- One operation is one second of run time. Every second started counts, and every run uses at least one. A five-second run uses five.
- Test runs count too. The runs your agent makes while it builds and tests use operations like any other run.
- The count starts again each month. The menu under your avatar shows ACT Operations used this month and the date of the Next reset.
Your plan also sets how many ACT automations can be active at once. The same menu shows it as ACT automations, for example 3 / 10 active. A paused automation frees its place.
The ACT Operations figure turns red when the month's operations are used up. Runs then start again after the next reset. To keep them running sooner, move to a plan with more operations. See Plan and billing.
How long can a run take?
A run has 150 seconds by default. If a job needs longer, ask the agent: "Give the nightly sync up to 10 minutes per run." You can also ask for retries: "If a run fails, try it once more." A run never takes longer than the operations left this month.
What happens when I remove the agent that built it?
Its ACT automations are paused. They keep their runs and code. Ask another agent with Automations allowed to rebuild what you still need.
Next: Build with an agent, or Triggers and webhooks.
