Flows
Steps that run when something happens.
A flow is one trigger and the steps that follow it. Mail arrives, a meeting ends, a task moves, the clock strikes nine: the steps run, and you see what they did.
A lot of a team’s week is the same small job done again: write up the call, draft the weekly update, check the inbox for a supplier’s reply. Each one starts with something that happened, and each one could start on its own.
Flows start on those moments. Because they run inside the workspace, their steps can read the call that just ended, the email that just arrived or the doc someone just wrote, and hand the result to a skill, a connected app or a document.
Runs when something happens.
Pick what starts the flow. Event triggers run at most 50 times a day each, so a busy inbox never runs away with it.
- New mail in your inbox, from anyone or one sender
- A message in a team chat channel, or one that mentions you
- A document created by someone on the team
- A meeting’s notes finishing, or a set time before or after a recurring meeting
- A task reaching a status, or a linked pull request opening, merging or closing
Runs on a schedule.
Run a flow hourly, daily, on weekdays, weekly, monthly, on a custom schedule, or once at a set time, in your own time zone.
Each step does one thing.
Steps run in order, and a step can use what an earlier one produced. On a status trigger, a step can carry a condition, such as a label, a priority, an assignee or a project.
- Run a skill, to report or to act
- Use a tool in one of your connected apps
- Call a web address with the event’s details
- Archive the meeting that triggered it
Ask for it, or lay it out yourself.
Tell the assistant what you want in plain words and it builds the flow. Or open the Flows page and set the trigger and steps on the canvas. Ready-made flows, like a weekly newsletter or a product doc from customer calls, are a click away.
Try it before you switch it on.
A test run works on a sample, a real task or meeting or a made-up one, and shows what each step would do. Nothing is delivered and nothing reaches anyone else.
Anything outward waits for your yes.
A step that writes to a connected app or posts somewhere waits for your approval card on each run. A flow that sends data out on its own switches on only from your card.
Every run leaves a record.
Each flow has its own agent that reports what it did. Results can land as a document, a notification or email drafts, and the run history shows every run, step by step.
