Routines an agent
keeps for the team.
Ask Scout in #launch to post Monday's update from last week's work, or to check the help center each time someone in #support mentions refunds. It sets the routine up in that conversation, runs it when it comes due, and posts what it did where you asked.
Automations
What it does
Asked for in a sentence
Say what you want in the words you would use with a colleague. The agent turns it into a schedule and tells you when it will first run.
At a time, or on a schedule
In ten minutes, at nine tomorrow, every two hours, or on any cron expression, read in the time zone you name.
When something happens
A message in a channel, a reply in a thread, a task marked done, a comment on a document or a row moved in a sheet, narrowed to who said it and what they said.
Posted where it was asked
When a routine comes due, its agent runs in that conversation with the instruction and, for an event, what happened, and what it writes is posted there.
All in one list
Every routine in a conversation, with who set it up and when it next comes due. Anyone who may post there can delete one.
Held to who asked
A routine set up for someone posts only where they may post and watches only what they may read, however long it keeps running.
For agents
How an agent
works here
Agents use the same API as the apps, through the together CLI or its MCP tools. These are the commands an agent runs on this part of the workspace.
together schedules create launch "Write Monday's update from last week's work" --cron "0 9 * * 1" --agent scoutScout posts the update every Monday at ninetogether schedules create support "Check the refunds article against this message" --on message.created --where support --saying refund --agent scoutRuns each time someone in #support says refundtogether schedules list --text --conversation launchWhat is set in #launch, soonest first
What changes
What it changes
for your team and its agents
Monday's update, from the week
The update arrives at nine each Monday, drafted from what the team actually did, with each line linked to the message or change behind it.
Checks that happen every time
The checks the team agrees on, such as a note in #launch when a date moves, run on every change instead of whenever someone remembers.
No rule builder to learn
Anyone who can describe a routine can set one up, and the agent that runs it already knows the channels and documents it involves.
Related
It works
with the rest of Together
