Starred Slack Messages to Notion Database...
Every 10 minutes, the agent finds starred Slack messages, generates a title and tags via AI, and saves them to your Notion database.
ops and IT teamsdevelopers and engineers
What it does
Capture important Slack messages instantly by having them organized into your Notion database every ten minutes. You get AI-generated titles and relevant tags for each starred message without any manual sorting.
Step by step
- Configure a scheduled trigger to run every ten minutes.
- Set up the Slack integration to fetch messages from the specified channel and filter for star emoji reactions.
- Map the extracted message content, link, author, and timestamp fields to the corresponding properties in the Notion database schema.
Where the LLM does the work
- Prompt the OpenAI model with the raw Slack message text to generate a concise, descriptive title for the Notion page.
- Instruct the LLM to select relevant tags from your predefined list based on the semantic context of the message content.
- Format the LLM output into a structured JSON object that can be easily parsed and mapped to the Notion database properties.
Watch out for
Notion property types must match the data format exactly, so ensure string tags are converted to multi-select options before creation.
LLM outputs can vary in structure, so implement robust error handling and fallback defaults if the model returns malformed JSON.
Tools that fit
The agent brief
Everything your agent needs, including the gotchas. Copy it and go.
You are helping me build the following AI agent workflow. ## Goal Starred Slack Messages to Notion Database...: Every 10 minutes, the agent finds starred Slack messages, generates a title and tags via AI, and saves them to your Notion database. ## Specification - What it does: Capture important Slack messages instantly by having them organized into your Notion database every ten minutes. You get AI-generated titles and relevant tags for each starred message without any manual sorting. - Trigger: On a schedule (Scheduled · every 10 minutes) - Autonomy: Fully hands-off - Expected setup effort: about an afternoon - Tools/services involved: - Slack: Fetching messages and detecting star reactions - Notion: Storing archived messages and tags in a database - OpenAI Chat Model: Generating titles and categorizing messages with AI ## Known pitfalls, handle each one explicitly in your implementation 1. Notion property types must match the data format exactly, so ensure string tags are converted to multi-select options before creation. 2. LLM outputs can vary in structure, so implement robust error handling and fallback defaults if the model returns malformed JSON. ## Reference implementation https://n8n.io/workflows/4502 (workflow template) Fetch and inspect this before building. If it matches my stack, adapt it; if not, rebuild the pattern with my tools. ## Process requirements 1. Before building: ask me which of the listed tools I actually use and what my platform is (n8n / Make / code / other). Do not assume. 2. Adapt the pattern to my answers; do not force the reference stack. 3. Address every pitfall above; tell me how you handled each. 4. Provide a test plan I can run before letting this touch real data. 5. Ask before any step that sends messages, modifies data, or spends money. Source: https://usecasesforagents.com/use-case/starred-slack-messages-to-notion-database-with-ai/ via usecasesforagents.com
Frequently asked questions
Can I use a different Messaging than Slack?
Yes. Slack is only the example messaging in this recipe. The same flow works with ClickSend API, Discord, Google Chat and LINE Messaging API. Swap the messaging connection and keep the rest of the setup as written.
Want this running in your business?
This is what I do. I design and build AI agents like this one, and keep them running. If you want it set up for your team instead of doing it yourself, get in touch.
Who it's for
Built for Ops-IT teams who need one more recurring task off a human's plate.
Developers can adapt this to their own repo or ticket queue with the same trigger and tools.