What this meeting follow-up agent handles
Meeting outcomes slip through the cracks when action items stay in notes or calendar invites. A Slack meeting follow-up agent handles the extraction and distribution of next steps while keeping an operator in control of the final post.
This setup is especially useful in three follow-up situations:
- Action item extraction. The agent reads meeting notes or transcripts, extracts action items with owners and due dates, and proposes a structured summary for posting.
- Decision logging. For meetings where decisions were made, the agent identifies key outcomes and proposes posting them to the project channel or decision log.
- Next meeting prep. The agent can propose scheduling follow-up meetings or surfacing pending items for the next session based on open action items.
How the agent works
The table below shows the trigger, inputs, outputs, and approval logic so you can judge operational fit quickly.
| Agent stage | What happens | Output | Approval |
|---|---|---|---|
| Trigger | A meeting ends, or meeting notes are saved to Slack, Notion, or a connected doc | Follow-up job starts | No approval for read phase |
| Inputs | Meeting notes, calendar event, participant list, previous action items | Extracted action items and decisions | No approval for data gathering |
| Proposed action | Post summary to channel, DM participants, create calendar events, or flag for manual review | Prepared Slack message | Approval before any write |
| Operator review | Reviewer checks summary accuracy, channel choice, and participant mentions | Approve, reject, or edit | Explicit approval required |
How to set up this agent
Describe which meeting types need follow-up, what should be extracted, and which channels should receive the summary.
Connect Slack and any meeting note sources with access to channels, message posting, and calendar integration.
Choose which follow-up types should always surface for review and which can be reviewed more quickly in batches.
Set notifications so the operator sees proposed follow-up messages quickly after meetings end.
Permissions and approval checks
- Read access should cover meeting notes, calendar events, and relevant Slack channels where context lives.
- Write scope should be limited to posting messages in approved channels and creating calendar events if configured.
- Sensitive meeting types should be flagged for manual review before any summary is posted publicly.
- Approval views should show both the extracted summary and the proposed channel routing before commit.
Frequently asked questions
Does the agent post follow-up on its own?
By default, follow-up proposals are surfaced for review before the message is posted to Slack.
How does the agent identify action items and next steps?
The agent reads meeting notes, chat transcripts, or calendar event descriptions, then extracts decisions, action items, and next steps. You describe which meeting types need follow-up, and the agent structures the output accordingly.
What happens if the follow-up format needs to change?
Update the agent description, review the new execution plan, and activate. The agent adapts to the new format without requiring builder edits or custom integrations.
Can the agent post to multiple channels based on meeting type?
Yes. The agent can propose posting to different channels based on meeting type, participant list, or tags. Channel routing works the same as message content: the proposal is reviewed before the post executes.