Skip to content

Automations

An automation is a task on repeat. It runs one of your agents, or an instruction you write, on a cadence you set — sweep the invoices every weekday at 7am, check a supplier portal every hour, send a summary on Monday mornings. Each time it fires, a new task starts on a computer in your workspace, works to the end, and opens at /tasks/<id> like any other task.

Open Automations from the sidebar, directly below Agents. The Work page has an Automations card that leads to the same place. You can also ask an agent in any task to set one up — see From a task.

Cadence reaches its next time (e.g. weekdays at 7am, Europe/Madrid)
→ Gates checked: business hours, anything to process, AI credit
→ A task starts: the agent's instructions, then the automation's
→ The agent works on its own computer until it is done
→ The run appears in the automation's run list

If a check fails, the run is skipped instead, with a reason, and the automation waits for its next time — see Skipped runs.

The page opens with one sentence that says whether anything is wrong — 2 need your attention. 6 are running fine., Everything is running fine. or Everything is paused. Below it, owners and admins see what automations cost this month; everyone sees which one runs next and when.

Filter by Workspace, Created by, Agent (each agent, or Freeform instruction) and Status (Active, Paused, Needs you, Failing), or search by name and instruction. The header switches between Cards and Timeline — your choice is remembered in this browser — and holds New automation.

Both views sort automations into the same sections, in this order. A section with nothing in it is not shown.

SectionWhat puts an automation there
Needs your attentionIts latest run is waiting for an answer or an OK, or its latest run failed
Working nowIts latest run is running
All goodEverything else
PausedIt is switched off

A run that is waiting or running keeps a paused automation out of Paused: pausing stops future runs, not the one already going.

When the system paused an automation rather than a person, the automation says why, on its card and on its page. Its agent was deleted means its agent is in the trash — recovering the agent resumes it. Paused by a product update marks the automations paused once, when agents lost their draft and paused states: the owner of each was shown a notice, We paused N automations, with a Resume button per automation, and Resume works from the automation too. A person who paused an automation by hand is not second-guessed: recovering an agent never resumes it.

Every card and every timeline lane says where its automation stands in words, with the button that fixes it beside it:

It saysThenButtons
Waiting for your OKHow long, and what it is askingAnswer, Open task
Failed, or Failed 3 in a rowWhy, and Next tryFix sign-in or Run again, and Pause
RunningHow long, and what it is doing—
✓ and the time of the last runWhat that run did—
SkippedThe reason—
Paused, or Paused · has never run—Resume

Fix sign-in appears when the failures were sign-ins that stopped working. It and Answer open the automation on that run, where you fix or answer in place.

A button only appears if you may use it. Answer shows only to someone who may answer that task; anyone else reads Waiting for an OK and gets Open task. Run again, Pause and Resume need you to be able to change the automation (see Who sees an automation). With Can use you get no buttons except Open task.

Each card’s … menu offers Details →, Configure, Run now, Pause / Resume, Share… and Delete to the people who may use them. Run now fires at once, through the same gates as a timed run, without moving the next time; a paused automation must be resumed first. Delete removes the automation; the finished tasks it started go with it and can be recovered for 30 days, like any deleted task. A task it started that is still working carries on as a task of its own.

Cards shows one card per automation: who does it, its cadence, the status line, the last and next run, and a strip of its last 12 runs.

Timeline fills the screen. Each automation is a lane, grouped by the same four sections, along a time axis you set to 12 h, 24 h, 3 d, 7 d or 15 d, with ‹ Now › to move back and forward. Finished runs are bars as long as they took; a run waiting for you or still running stretches to Now; skipped runs and the runs coming up are marked along the lane. When an automation’s sign-in has expired, its next run reads will fail: sign-in expired before it happens. Hover a bar for what that run did; click a bar, or a lane’s name, to open the automation on that run.

Clicking a card opens the automation over the page. On the left: one sentence — Runs weekdays at 7:00 AM (Europe/Madrid). Next: tomorrow., or Paused. — who does the work and with which connectors, the tiles Cost this month (owners and admins only), Computer time this month, Runs this month and Done, the Last 12 runs, and Run now and Edit.

On the right, every run, newest first: its Outcome, When, how long it Took, What happened and, for owners and admins, its Cost. Search the runs or narrow them with the Outcome filter. Selecting a run opens it in place: what it did, the files it made, the question it is waiting on (answer it there), and fixes such as Update sign-in to … or Run again when it failed. A running run offers Watch → for its live view. Open a run to go to its task.

Details → in the … menu opens the automation’s full page: its cadence, what it does each time, its gates, and its history with every skipped run’s reason.

New automation opens a panel with two ways in, Chat and Form. Both fill in the same draft, so you can switch between them without losing anything.

Chat — the automation assistant asks, one question at a time: when it should run (saying which time zone it used), who does it — one of your agents, or an instruction you write — what it should do, whether it should ask before acting (only when the job sends or changes something), and a name. Under its latest reply, a short list shows the automation so far — When, Who, What, Approval and Name — exactly as it will be created. If you already have as many automations as one person may, it says so first. It ends on Create automation or Keep editing, and then offers to run it once to test. Nothing is saved until you choose Create automation.

Form — the same choices as fields:

  1. Name — such as Morning invoice sweep.

  2. Agent — which agent does the work, or No agent — free-form. With an agent, its instructions come first and the automation’s follow. A deleted agent does not run. The agent cannot be changed later — create a second automation instead.

  3. What it does each time — the instruction for every run. Optional with an agent; the whole job without one.

  4. When it needs your approval — Autonomous (the default) runs to the end without asking anyone. Interactive stops and waits for you before sending, deleting, buying or submitting.

  5. Cadence — Hourly, Daily, Weekdays, Weekly or Custom cron (five fields, e.g. 0 9 * * 1-5), with a preview of the next run, and the Timezone it is read in — so a 7am automation means 7am where the work is, whoever edits it later.

  6. Gates — optional checks before each run (below).

Configure, in a card’s … menu, opens the same panel with the automation loaded: What do you want to change? You never choose a computer: each run gets one in your workspace when it fires.

GateWhat it does
Skip when there is nothing to processLooks first — in the place you describe under Where to look, such as unpaid invoices older than 30 days — and skips the run if there is nothing to do
Only fire during business hoursSkips runs outside From – Until on the days you pick, in the automation’s own timezone
Pause after repeated failuresPauses the automation after a number of Consecutive failures (5 by default)

These apply to everyone, owners included:

  • An automation runs at most once every 30 minutes.
  • One person’s automations that are switched on must run at least 30 minutes apart from each other. Paused ones do not count.
  • One person can have at most 10 automations, paused ones included. Delete one to make room.

A save that breaks a limit is refused with the reason and what to change.

An automation does not use your own Settings → Approvals. An Autonomous one keeps running on its own at any level. An Interactive one follows its agent’s approval level, so an agent set to Approve all except final acts only stops at a final act.

An Interactive automation stops at the first action that needs an OK: it moves to Needs your attention, reads Waiting for your OK, and the waiting task reaches you in the Inbox. Answer opens the run, where you approve or decline without leaving the page.

A run that cannot or should not go ahead is recorded as Skipped, with a reason, before any work starts. The common ones:

ReasonWhat happened
Agent busyThe agent was already working on another task
Previous task activeThis automation’s previous run was still working
Nothing to processThe nothing to process gate found nothing to do
Outside business hoursThe business-hours gate was closed
Could not check for workThe nothing to process gate could not look
Paused after failuresThe automation paused itself after repeated failures
Agent deletedThe agent was deleted. Recover it to run the automation again
Agent no longer sharedThe automation’s creator can no longer use its agent
No AI creditThe account has no AI credit to spend. It runs again at its next time once credit is added
Missed windowThe run’s time had already passed

A skip never piles up work: the automation carries on from its next time, without replaying the runs it missed. Agent busy, Previous task active and Nothing to process are quiet — they are expected, and send no notification. Every other skip notifies the people who can see the automation.

An automation runs as the person who created it — their browser, their sign-ins, their account’s credit. It is theirs until they share it; the chip on its page shows who has access, and selecting it opens the share box.

PersonWhat they can do
The person who created itEverything, including deleting it
Can editChange it, pause it, Run now, share it
Can use, or Everyone in ‹workspace›See it and every task it has started, read-only
Workspace owners and adminsSee every automation in their workspaces, with what it costs; change, pause, run and delete it

An owner or admin who cannot use the automation’s agent may still rename it, change its cadence, pause or delete it, but not run it or change its instruction. Anyone who can see an automation sees all of its tasks. In the Tasks list each of them carries an Automation: marker with its name.

If the person who created an automation leaves the workspace, it is paused so it stops spending credit. An owner can turn it back on. See Sharing.

You can ask an agent in any task to list, create, change, pause, resume, run or delete an automation — “check the supplier portal every weekday at 8”. It uses the built-in aptiveai_automations skill, and every change stops on an approval card first — The agent wants to create an automation ”…”. Allow it? The change is made as you, under the same rules and limits as the Automations page. A task an automation started can never change automations itself.