Stephen Turner
Akash Kumar
Jordan Lee
Taylor Scott
Use a scheduled AI agent to write a weekly meeting digest
A weekly meeting digest agent runs on a schedule, reads the week's meeting notes and writes one short summary: decisions made, action items still open and risks raised. In Bridge you build it as a custom agent with notes search and a scheduled trigger. It can leave the digest in Bridge or post it to a Slack channel.
What the agent does
Reading every recap from a busy week takes longer than the meetings deserve. A digest agent does the reading on a fixed schedule and hands back one page.
It looks backwards. That's different from Bridge's Sunday evening email, which previews your upcoming week's meetings.
Inputs, actions and output
Every agent can read transcripts. Turn on notes search so it can search previous meeting notes for context.
| Part | In Bridge |
|---|---|
| Trigger | Scheduled: an interval, time, start and end date, and timezone |
| Input | Your meeting notes, through the agent's notes search tool |
| Action | Writes the digest; with Slack connected, can post it to a channel |
| Output | A chat on the workspace Assistant page or under Chats, or a Slack message |
Set it up
- Select Create Agent from the sidebar, name it and write its instructions.
- In Tools, turn on notes search. Connect Slack first and select it if the digest should be posted there.
- In Triggers, choose Scheduled. Set it to repeat every week, pick a time, start date and timezone, and check the next-occurrence preview.
- Save. Results appear on the workspace Assistant page or under Chats.
Illustrative instructions
Instructions can run to 4,000 characters, but short and specific works better. An example for a product team's digest:
- Search notes from meetings in the last seven days that involve the product team.
- List decisions made, one line each, with the meeting they came from.
- List action items that are still open, with owner and due date if stated.
- Flag risks or blockers raised in more than one meeting.
- Keep it under 250 words. Don't guess an owner or date that wasn't said.
Test it before you schedule it
Every agent also answers when you @mention it in the Assistant. Run it by hand on last week's meetings and compare the digest with the recaps.
Check that it found the meetings you expected and invented nothing. Adjust the instructions, then turn on the schedule.
Human control and limits
The digest only covers what's in your meeting notes. Meetings nobody captured won't appear, so treat it as a summary of the record, not of everything that happened.
- Posting respects your Slack permissions: the agent only uses channels you can access.
- Choose the Slack channel with care, since a digest can repeat sensitive details from private meetings.
- Set an end date for a digest tied to a project, so it stops when the project does.
- Agents and scheduled triggers need a paid plan.