Slack
After each finished meeting we post five short lines to the channel: the title and source, the summary, the number of action items, a watch-out count if there is one, and the link to the full minutes. It is a notification, not the minutes — a channel full of pasted transcripts gets muted.
Checked 2026-08-29 · every step is done on your Flows page or inside Slack; nothing here needs support.
On Slack's side
- In Slack, create an incoming webhook for the channel that should receive the posts — look for Incoming Webhooks in your workspace's app settings, add it to the channel, and copy the webhook URL (it starts with hooks.slack.com).
- On your Flows page add a destination of kind Chat channel, provider Slack, and paste the URL.
- Tick "Only send meetings with a watch-out" if the channel is for escalations rather than every call.
What to paste from your flow card
- Into MeetNotes: the incoming webhook URL. It is stored encrypted; only its prefix is shown afterwards.
What we never ask for: A Slack bot token, admin rights, or read access to the channel. An incoming webhook can only post.
How to test
- Click "Send test" on the destination. A sample message arrives in the channel within seconds.
- If it does not, the URL was revoked or pasted incompletely — create a fresh webhook in Slack and add the destination again.
When an event shows failed or skipped
The Flows page prints one short reason per event. Here is what each one on this connector means and what to do.
delivery failed— Your endpoint, channel or CRM did not accept the post — it was unreachable, answered with an error, or timed out. We retry, then mark the delivery failed. Use "Send test" on the destination after you have checked the URL or token.
The full list, across every connector, is on the setup index.
Ready to connect it?
Open your workspace's Flows page — managers and owners see it under the team.
