Skip to content

Slack Thread Summariser

Example prompt: "When a Slack thread in #product-decisions gets more than 15 replies, summarise the discussion and post a TL;DR at the bottom of the thread."

The Problem

Long Slack threads are where decisions get made — and where context gets buried. A 40-reply thread about a product launch might contain three key decisions, two action items, and a lot of back-and-forth. Anyone joining the conversation late has to read every message to figure out what was actually agreed. In practice, most people just skip the thread entirely and ask someone to repeat the outcome, which wastes everyone's time twice.

How GloriaMundo Solves It

We build a workflow that monitors designated Slack channels for threads that cross a reply threshold you set — say, 15 messages. When a thread hits that mark, an integration step fetches all the messages in the thread, including any linked documents or images mentioned. An LLM step reads the full conversation and produces a structured summary: the main topic, key points of agreement, unresolved questions, and any action items with owners. The workflow then posts this summary as a reply at the bottom of the thread, clearly formatted so it stands out from the discussion. Glass Box preview lets you see the summary before it gets posted, so you can tune the level of detail.

Example Workflow Steps

  1. Trigger (composio_event): Fires when a Slack thread in a monitored channel exceeds the configured reply count.
  2. Step 1 (integration): Fetch all messages in the thread from Slack, including sender names and timestamps.
  3. Step 2 (LLM): Summarise the conversation into key points, decisions made, unresolved questions, and action items with owners.
  4. Step 3 (integration): Post the formatted TL;DR summary as a threaded reply in Slack.

Integrations Used

  • Slack — source of thread messages and destination for the posted summary

Who This Is For

Product managers, engineering leads, and operations teams who rely on Slack for decision-making and regularly deal with long threads where important context gets lost in the noise.

Time & Cost Saved

Reading and mentally summarising a 30-message thread takes roughly 5-10 minutes. In a busy team with several long threads a day, that adds up to 30-60 minutes across participants who need to catch up. This workflow produces an accurate summary in seconds and costs a small number of credits per run — one LLM call plus two integration steps.