Write it once, it runs on schedule.
An automation is a message the assistant runs for you on a schedule, as a normal chat turn, while you are on site. You write the message once, pick when it runs, and each run lands in a chat you can open, with a notification carrying the summary.
Available on
What you can do
Four parts: name, prompt, schedule, target
The prompt is the message the assistant receives on every run, written exactly as you would type it in the chat. The schedule is once at a given time, every day, weekdays, one day a week, or every so many minutes, with an optional last day.
Every run lands in a chat
Choose a fresh chat for every run, or one chat of yours that wakes up each time and keeps its context: the list, the table and the decisions you made together. The notification carries the summary; the chat holds the full result.
Reads what is already in your project
A run can search your project, read documents, open the issues log, read the tracker and the planner, search the web if you leave that on, and read the services you have connected. Nobody is there to answer a question, so it decides, states its assumption in a line, does the work and ends with a summary.
The reports the week already asks for
Monday, the open issues older than 14 days grouped by assignee and system. Every evening, what changed today. Friday, the look-ahead from the planner and the required documents past their due date in the tracker. The evening before a witnessed test, a readiness check on that asset.
Create it on the Automations page or from any chat
The page has a month calendar, the day's agenda and your list; New automation asks for the name, the prompt, the schedule, where it runs and the mode. Or type "Every Monday at 07:30, list the open issues older than 14 days in a new chat, read-only" in a chat and the assistant creates it, and can later pause, resume, reschedule, rewrite or delete it.
A runs log for every firing
Run now fires one immediately so you see what comes back before you trust the schedule. The Runs tab lists every firing with its status, how long it took, its summary and a link to the chat it worked in. Three failures in a row pause the automation and you get a notification saying so.
How a team uses it
- 1
An engineer writes the message as a brief to a colleague who starts at seven: the scope, what to produce and in what order, the thresholds, and the one line to finish with.
- 2
They pick the schedule and the mode: read-only for a review, changes allowed when the run should draft something.
- 3
Run now shows what comes back. They adjust the words, then let the schedule take it.
- 4
Each morning the notification carries the summary and the chat has the full list, so the meeting starts from a list instead of from memory.
- 5
A once-only automation switches itself off after it runs and stays in the list to run again by hand; one with a last day ends quietly on that date.
In more detail
Two modes for a run
Read-only means the run can look at everything you can look at and change nothing: no issue created, no comment added, no document edited. Changes allowed lets a run draft, for example one email per assignee with their overdue issues, left in your connected Outlook or Gmail mailbox; sending stays off unless you switch Allow sending email on for that automation, and only Outlook can send. An unattended run never deletes anything, never changes who is in a project or where files live, and anything that would have shown an approval card in a normal chat is refused and noted in the summary so you can do it by hand.
Yours alone
The automation runs with your access, your connected services and your limits. Project members never see your automations. A project on the automation is a filter for the run, not a share.
Limits today
Up to 10 automations per account and 20 runs per day across all of them; two runs at the same time. Intervals from 15 minutes to 7 days, in your time zone. Prompts up to 8,000 characters. The runs log is kept for six months; the chats a run worked in are kept like any other chat.
On the phone
The Automations screen shows the list with the countdown, the runs and their summaries, and lets you run one now, pause, resume or delete it. Creating and editing happen on the web or by asking the assistant.
Questions
Yes. Target the chat you are in and every run is one more message in that conversation, so the assistant keeps the list, the table and the decisions you made together. "Every weekday at 07:00 until the 14th, continue this review" is enough for the assistant to set it up.
The runs log says which state it ended in. Stopped early means it hit a limit; open the chat and you find where it got to, and it is told to continue up to a number of extra turns you set, three by default. Failed means it could not start or errored. Missed means the time slot was more than six hours old by the time it could run, for example after a service stop.
No. Nobody is there to answer, so the assistant is told not to ask. It decides, states its assumption in a line, does the work and ends with the summary you read in the notification. Write the thresholds and the grouping into the message so there is nothing left to ask.
Ready to see your next project clearly?
Bring assets, issues, documents, and schedule into one place — and put an AI assistant that knows your project next to every engineer.
No credit card required · Web, mobile & Office