n8n Slack Bot + AI Agent: Answer Team Questions from Your Docs
Your team asks the same question in Slack every week. Wire a Slack Trigger to an n8n AI agent with a vector store and the bot answers from your own documents, in the thread, in seconds.
118 tested guides on AI agents, n8n, RAG, and automation — newest first.
Your team asks the same question in Slack every week. Wire a Slack Trigger to an n8n AI agent with a vector store and the bot answers from your own documents, in the thread, in seconds.
The built-in AI nodes cover the common cases. But batching rows, reshaping API responses, and building scoring functions hit a wall fast. The Code node fills the gap with JavaScript wherever the visual nodes cannot reach.
A new lead arrives with nothing but a name and email. An n8n workflow pulls company data, scores the lead with an AI agent against your ICP, and routes it to the right rep or drip sequence before anyone opens a browser tab.
Customer feedback arrives from five places and nobody reads most of it. An n8n workflow with an AI agent classifies every piece by sentiment and theme, routes urgent complaints immediately, and builds a weekly digest your product team can act on.
A contract lands in a shared Drive folder and sits unread for three days. An n8n workflow detects the file, extracts the text, runs it through an AI agent, and posts a structured summary with key dates and parties before anyone opens it.
A context window is the token budget for one request, and input plus output share it. Bigger windows hold more text but do not read it all equally: the lost-in-the-middle effect means facts buried mid-context get recalled worse. Here is how tokens, limits, and placement actually
Most n8n frustration is a data-shape misunderstanding, not a broken node. Every connection carries an array of items, each with a json key. Once you can picture that shape, $json, $('Node Name'), and the 'Referenced node has no data' error all make sense.
You record every call and still lose the decisions. This is an honest, end-to-end n8n build that turns a meeting recording into structured notes plus routed action items, with straight talk on the Whisper file limit, missing speaker labels, per-minute cost, and consent.
Your agent gave a wrong answer and you have no idea where it broke. Observability captures the run (every LLM call, tool call, prompt, and cost) so you can replay it and point at the exact failing step. Here are the three pillars, what to log per step, and when a dedicated tool
Plain RAG embeds chunks that have lost their document context, so 'revenue grew 3%' matches nothing useful. Contextual retrieval writes a short per-chunk context and prepends it before embedding and BM25. Here is the method, the build, and the honest ingest trade-off.
You turned the temperature up and the model got more creative, down and it got smarter. Both stories are wrong. Temperature and top-p only reshape how the next token is drawn. Here is what each setting really does, top-p versus top-k, and which value to use per task.
Microsoft folded two of its biggest open-source agent projects, Semantic Kernel and AutoGen, into a single production SDK with version 1.0. Here is what the Microsoft Agent Framework bundles, where it sits against LangGraph, CrewAI, and OpenAI's Agents SDK, and how a small team