Automations and briefings
Choose between an update you review before sending, a built-in Workspace briefing, and your personal daily briefing.
concept · new-user
Use an automation to prepare a recurring update from your Workspaces. You choose what it covers, when it runs, who receives it, and how it reaches them. Scheduled and after-meeting update automations produce a draft for their owner to review before sending.
Choose the right kind of update
| You want to… | Use | Where to manage it |
|---|---|---|
| Review a weekly stakeholder update or a follow-up after a matching meeting | An update automation | Automations in the sidebar; Settings → Account → Automations in the earlier layout |
| Give a Workspace its daily, weekly, or monthly summary | A built-in Workspace briefing | Settings → [Workspace] → Briefing and automations |
| Read your own daily view across your work | Your personal daily briefing | Home or Today’s briefing; delivery settings under Account → Notifications |
Built-in Workspace briefings are marked Built in and Sent automatically, no approval needed. They use the Workspace’s schedule and delivery settings. They do not wait in your personal automation draft queue.
Your personal daily briefing is separate from both. Changing a Workspace briefing does not change your personal briefing time.
What an update automation contains
An update automation records:
- the Workspaces it draws from;
- a schedule, or an after-meeting trigger based on meeting types or a calendar series;
- the sections to include, such as progress, risks, decisions, or next steps;
- the intended recipients and delivery channel;
- the tone of the update.
Suggested recipes provide starting points, such as a weekly leadership update or meeting follow-through. Review the resulting configuration rather than assuming a recipe already matches your audience or reporting period.
The automation’s owner manages it and reviews its drafts. Being the Owner of a source Workspace does not make you the owner of another person’s automation.
From draft to delivery
For scheduled and after-meeting update automations, a run prepares a draft. Open Review draft, check the text and audience, then choose Approve & send or Skip this one. You can edit the draft before approving it.
Approval and successful delivery are separate. Check Run history and its delivery results if a recipient did not receive an update. A sent update can still have a failed or queued delivery to a particular destination.
These instructions cover scheduled and after-meeting update automations. Other automation types may have different availability and sending rules; check the trigger and delivery description shown for that automation.