Block 1 - OpenRouter Chat Model
- Type / Role
- @n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Slack quietly released an update to their API that allows developers to build "AI Apps & Agents", which is a special classification of apps that have access to several special capabilities includin...
@n8n/n8n-nodes-langchain.lmchatopenrouter, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.noop, n8n-nodes-base.slacktrigger, n8n-nodes-base.if, n8n-nodes-base.httprequest, n8n-nodes-base.slack, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by James Francis.
Original n8n.io sourceSlack quietly released an update to their API that allows developers to build "AI Apps & Agents", which is a special classification of apps that have access to several special capabilities including:
This workflow demonstrates how to build a Slack agent that takes advantage of all of these features.
For a full video walkthrough of this workflow, watch this YouTube tutorial.
All of the below steps are required for this workflow to function properly unless otherwise noted.
assistant:writechat:writechannels:readim:historymessage.imIn order to save the chat history and give your agent a working memory, you'll need your own Postgres database. You can use Supabase, Neon, or any other Postgres database provider. Once you've added your database's credentials to n8n, you can select those credentials in the Postgres Chat Memory node. This worklow saves all chat history in a table called chat_histories, but you name the table whatever you want.
You'll need to create the following credentials:
Now that you've created your Slack app, have your Postgres database, and have created credentials, follow these steps to wire up your workflow:
Once you've completed the setup process and added in your credentials, you'll have a fully functional Slack chatbot complete with threads, loading UI, and the ability to pin your app to your workspace's top bar.
Now that this skeleton app is in place, it's up to you to add horsepower to the AI agent at the center of it all. Customize the prompts and add whatever tools you'd like. The sky is the limit!
If you have any questions or feedback about this workflow, or would like me to build custom workflows for your business, email me at [email protected].
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Create a Slack AI chatbot with threads & thinking UI using OpenRouter & Postgres |
|---|---|
| Complexity | intermediate |
| Nodes | 12 |
| Categories | Support Chatbot, AI Chatbot |
| Author | James Francis |
| Published | 07 Jul 2025 |
Use the JSON export at /data/workflows/5749/5749.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Slack quietly released an update to their API that allows developers to build "AI Apps & Agents", which is a special classification of apps that have access to several special capabilities includin...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Support Chatbot, AI Chatbot use case.