Overview
The same work, without you asking each time
An automation is a piece of work plus a schedule. "Every Monday at 9, check for supplier price changes since last week and summarize what moved" is an automation. It does exactly what it would do if you asked for it by hand, on the day and time you picked.
Automations only ever see what the person who set them up can see. If that person loses access to something, the automation loses it too.
- A piece of work plus a schedule
- Describe the work once, then pick how often it should happen.
- Runs on the day and time you pick
- It does exactly what it would do if you asked for it by hand.
- Sees only what its owner can see
- An automation is limited to the access of the person who set it up.
- Daily spending ceiling
- Each automation carries its own limit on what it can spend in a day.
Tip
Quick Start
Put your first piece of work on a schedule
Open Automations
Open Workspace → Agents → Automations (when Automations is enabled for your org).
Name it and describe the work
Give the automation a name, then describe what you want done.
Pick how often
Choose the schedule it should run on, for example every Monday at 9.
Review and confirm
Press Review to see the summary card. Nothing is created until you confirm it.
Setting One Up
You see everything before it exists
Give it a name, describe the work, and pick how often. Press Review and you get a summary card. Nothing is created until you confirm that card.
- What will run
- The work you described, in full.
- When it will run
- The schedule you picked.
- Who can see it
- Who in the organization the automation is visible to.
- The most it can spend in a day
- Its daily ceiling, before anything runs.
- Where your AI usage stands
- How much of this month's AI usage you have left, before anything runs.
Tip
What It Can Cost
A daily ceiling on every one of them
There is no cap on how many automations you can create. Create as many as you find useful: the number of automations is never what you pay for.
What costs something is the work they do. Automation runs draw the same AI usage pool as your chats, tasks, agent conversations, and content creation, so a schedule that fires hourly uses more of that pool than one that fires weekly.
- Per-automation daily limit
- Each automation carries its own daily spending limit. If a run reaches that limit, it stops for the day and records why, rather than continuing quietly. That limit is a safety rail against something running away. It is not a bill.
- Shared AI usage
- Runs draw your organization's monthly AI usage allowance, the same pool your chats and content creation use. There is no separate automation meter and no limit on how many you create.
Missed Runs
Nothing is skipped quietly
If a scheduled run could not happen (a maintenance window, for instance), the automation shows how many runs were missed and why.
Important
When One Turns Itself Off
It always tells you the reason
Before every run, an automation re-checks that it is still allowed to run.
- Owner still has access
- The person who owns it is still on the team with the right access.
- Material still available
- The material the work depends on is still there.
- Billing current
- The organization's billing is up to date.
If any of that has changed, it turns itself off and records why instead of running anyway or skipping in silence.
The reason appears on the automation. Fix what it names, then turn it back on. It picks up at the next scheduled time, and never tries to make up for the time it was off.
Who Can See and Change Them
No hidden automations
- Your own automations
- You can see them, pause them, and turn them back on.
- Administrators and owners
- They see every automation in the organization, including who set each one up and what it has cost.
That is deliberate. Nothing should be running on the company's knowledge that the company cannot see.
Making an automation visible to everyone in the organization is an administrator action.
Stopping Everything
One button, whole organization
Administrators have a "Turn everything off" action. It stops every automation in your organization at once and records that it was turned off deliberately. Use it if something looks wrong and you would rather sort it out with nothing running.
Nothing is deleted. Each automation keeps its schedule and its history and can be turned back on individually.
Tips & Best Practices
Getting good results on a schedule
- Ask for something that changes
- "Summarize what moved since last week" gives you a useful message every week. "Summarize our supplier contracts" gives you the same message every week.
- Start with a weekly schedule
- If it turns out to be worth more often, change it. The other direction usually means noise you learn to ignore.
- Give it a clear finish line
- The same as a task. An automation that ends somewhere produces something you can read in a minute.