What this automation does
When a Slack thread reaches a certain length or gets a specific emoji reaction (like a bookmark), this automation reads the entire thread, uses AI to extract a summary, key decisions, action items, and owners, then creates a structured page in your Notion workspace.
This solves the universal problem of important decisions getting buried in Slack. Instead of someone manually writing meeting notes or combing through threads, the AI does it in seconds. Works especially well for teams that make decisions asynchronously in Slack channels.
Tools you need
- Slack (Business+ or Enterprise): Thread access via API — needs permission to read channel messages
- OpenAI API (GPT-4): Summarizes threads and extracts structured data ($0.02-0.05 per thread)
- Make (Integromat): Connects Slack trigger to OpenAI processing and Notion page creation
How to set it up
Step 1: Create a Make scenario triggered by a Slack reaction event. Filter for a specific emoji like :memo: or :bookmark: — this lets team members flag threads worth saving rather than processing everything.
Step 2: Use Make's Slack module to fetch the full thread (all replies) from the parent message. Concatenate them into a single text block with sender names and timestamps.
Step 3: Send the thread text to OpenAI with a system prompt that asks for: a one-paragraph summary, a list of decisions made, action items with assignees, and any unresolved questions. Ask for the output in JSON format.
Step 4: Parse the JSON response and create a Notion page in your designated database. Map the summary to the page body, decisions to a toggle block, action items to a to-do list, and tag it with the Slack channel name and date.
Cost breakdown
| Item | Cost | Notes |
|---|---|---|
| Make | $10-$20/mo | Based on number of scenarios and operations |
| OpenAI API | $10-$25/mo | ~$0.03 per thread at 300-800 threads/mo |
| Notion | $0 (included) | Uses your existing Notion workspace |
| Setup time | 25-40 min | One-time configuration |
| Total monthly | $20-$45/mo | Saves 3+ hours of manual note-taking per week |
Frequently asked questions
Slack's free plan limits message history, which can cause issues with older threads. For reliable access to all thread messages via the API, you need Slack Pro or Business+. The automation itself works the same way regardless of plan.
Absolutely. The Notion page structure is fully controlled by the Make scenario. You can add custom properties like project tags, priority levels, or department labels. Some teams also add a link back to the original Slack thread for context.