Route every Otter.ai meeting recap to the right Slack channel

Build an agent workflow that runs whenever a meeting finishes in my Otter.ai workspace. Trigger it from an Otter Workspace Webhook subscribed to the conversation.completed event so it fires the moment Otter is done processing the conversation.

From the webhook payload, read the meeting title, participants, summary, and transcript. Use those to draft a Slack-ready recap with these sections in order: a one-line TL;DR at the top, three to five bullet decisions, action items with owners and due dates whenever they are stated (omit owner or date if it is not stated rather than guessing), and any open questions. Format the message in Slack mrkdwn so it renders cleanly when posted: use single asterisks for bold and dashes for bullets.

Pick the destination channel intelligently from a configured allowlist. The allowlist is an editable list of channels the agent is allowed to post into. Each entry has a channel name plus optional topic keywords or customer names. At run time, call the Slack Bot List Channels operation to fetch current channel names and purposes, then score each allowlisted channel by comparing the meeting title and summary against the channel name, the channel purpose, and the configured keywords. For example, a weekly product sync meeting should route to #product, a meeting with a customer name in the title should route to that customer's account channel, and an engineering retro should route to #eng-retros.

If no channel scores above a configurable confidence threshold, fall back to a default channel like #meeting-notes and @-mention the meeting host so they can forward it. Require an explicit default fallback channel at setup time. Never post into a channel that is not on the allowlist, even if it appears to match.

Once a destination is chosen, call the Slack Bot Send a Message operation to post the formatted recap. Include a header line above the TL;DR with the meeting title, date, duration, and participant count.

Use the Slack Bot integration (not the user-token Slack integration) so the post is attributed to a workspace bot rather than to a specific person. The goal is that nobody manually shares notes after a meeting, and the right team sees a tight, accurate recap within a minute or two of the call ending.