Summarize & reply to Slack channel messages with Claude AI assistant
β¨ What It Does
Mello is a Claude-powered Slack assistant that helps you stay on top of unread messages across all your channels.
It:
- Summarizes conversations contextually using Claude AI.
- Generates reply suggestions and sends them as private (ephemeral) Slack messages.
- Lets you respond instantly with one-click AI-suggested replies.
Perfect for busy teams, founders, and anyone looking to reduce Slack noise and save hours each week.
π§ Setup Instructions
-
Create a Slack App
- Go to Slack API β Your Apps
- Click Create New App and set it up for your workspace
- Under OAuth & Permissions, add:
- Bot Token Scopes:
commands,chat:write,channels:history,users:read - User Token Scopes:
channels:history,chat:write
- Bot Token Scopes:
- Enable Interactivity, and point the Request URL to your n8n webhook (e.g.
/slash-summarize)
-
Add Claude API
- Get an API key from Claude (Anthropic)
- In n8n, set up the Claude API credential (or switch to OpenAI)
-
Import This Workflow
- Go to your n8n instance, click Import, and paste this template
- Update any placeholders (Slack app, Claude key, webhook URLs)
- Follow the inline sticky notes for guidance
-
Test It
- Type
/summarizein any Slack channel - Mello will fetch unread messages, summarize them, and show reply buttons in a private message
- Type
β± Setup time: ~10 minutes
π Workflow Highlights
- Slash command trigger (
/summarize) - Slack API integration to fetch messages
- Claude AI for contextual summaries
- Reply suggestions with smart buttons
- Private Slack delivery (ephemeral messages)
- Designed to be easily extended (e.g. add support for OpenAI, custom storage)
π Note
This is a lite preview of the full Mello workflow.
β The full version includes:
- Slack reply buttons with thread context
- Full OAuth flow with token storage
- MongoDB integration
- Custom Claude/OpenAI configuration
- Hosted version with onboarding, branding & support
π‘ Want access to the complete version?
π© Email nina@baloon.dev
Summarize & Reply to Slack Channel Messages with Claude AI Assistant
This n8n workflow automates the process of summarizing Slack channel messages using Claude AI and then replying to the channel with the summary. It's designed to help keep team members informed about lengthy discussions without needing to read every message.
What it does
- Receives Slack Messages: It listens for incoming messages from a configured Slack channel via a webhook.
- Extracts Message Content: It extracts the relevant text content from the incoming Slack message.
- Summarizes with Claude AI: The extracted message content is then sent to the Anthropic Claude AI model for summarization.
- Replies to Slack: The generated summary from Claude AI is posted back to the original Slack channel.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Slack Account: A Slack workspace and a channel where the bot will listen and post.
- Anthropic API Key: An API key for the Anthropic Claude AI service. This will need to be configured as a credential in n8n for the "Anthropic Chat Model" node.
- Slack App/Webhook: A Slack App configured with a webhook URL that points to this n8n workflow's webhook trigger. The Slack App will need permissions to read messages and post to channels.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Webhook:
- Once imported, activate the "Webhook" node.
- Copy the "Webhook URL" provided by n8n.
- In your Slack App settings, configure an "Outgoing Webhook" or an "Events API" subscription to send messages from your desired channel to this n8n webhook URL. Ensure the Slack App has the necessary permissions (e.g.,
channels:history,chat:write).
- Configure Anthropic Credentials:
- Click on the "Anthropic Chat Model" node.
- Under "Credentials", select or create a new "Anthropic API" credential.
- Enter your Anthropic API Key.
- Configure Slack Reply:
- The workflow currently uses a generic "HTTP Request" node to post back to Slack. You will need to configure this node:
- Method:
POST - URL: This should be a Slack Incoming Webhook URL for your channel, or a Slack API endpoint if you prefer.
- Headers: Set
Content-Typetoapplication/json. - Body: Construct a JSON body that includes the summary from the "Basic LLM Chain" node. A typical Slack message body might look like:
(Adjust{ "text": "Summary of recent messages: {{ $json.text }}" }{{ $json.text }}based on the actual output field name from the LLM Chain node).
- Method:
- The workflow currently uses a generic "HTTP Request" node to post back to Slack. You will need to configure this node:
- Activate the Workflow: Save and activate the workflow.
Now, when messages are posted in the configured Slack channel, the workflow will trigger, summarize them using Claude AI, and reply with the summary.
Related Templates
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chatβturn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. π What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing π§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation π Required Credentials OpenAI API Setup Go to platform.openai.com β API keys (sidebar) Click "Create new secret key" β Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β Dashboard β API Keys Generate a new API key β Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βοΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβchat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" π― Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration β οΈ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch π LinkedIn β Wessel Bulte
π How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From β senderβs email address To β recipientβs email address Subject β email subject line Summary β short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits β Full Automation: Eliminates manual reading and data entry from incoming emails. β Multi-Source Integration: Handles data from different email providers seamlessly. β AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. β Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. β Time Efficiency: Processes emails in real time, improving productivity and response speed. *β Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.