Slack Company Brain With n8n and Claude: How the Design Works
By Matt Cullerton, founder of Mavric and Apso
A "company brain" in Slack is a bot that answers team questions from a set of shared documents and refuses when the answer is not there. A TikTok from @pro.glitch (Professor Glitch) shows one built with Slack, n8n, Claude Sonnet and Google Drive. The design is sensible and the frames match the description, but the company in the demo is fictional, and the key safety check, matching quotes against real pages, is described rather than shown.
The saved copy of this video had no audio track or transcript, so this breakdown relies on the frames and the post description.
What tools does the Slack company brain use?
A diagram labeled "1 FOUR TOOLS" assigns one job to each:
- Slack: "where the team talks"
- n8n: "the wiring"
- Claude: "the AI · Sonnet"
- Google Drive: "where the brain lives"
The description says the system runs "three AI workflows, using n8n's built-in AI agent with Claude Sonnet." The frames show one of them, an n8n AI Agent node titled "File it into the brain (AI Agent)". Its system prompt begins "You file new facts into Harborline's company brain: Google Docs pages." Max Iterations is set to 10 and "Return Intermediate Steps" is on. The other two workflows, filing from an Inbox folder and a Monday report, appear only in the description. Neither the video nor the description says which Sonnet version is used.
n8n's Anthropic Chat Model node is the sub-node for using Claude chat models with conversational agents, which fits this setup.
How do facts get into the brain?
According to the description:
- A manager adds a ✅ reaction to a Slack message.
- n8n checks an approvers sheet.
- The original message is saved to a Raw folder.
- The agent updates the relevant Google Docs pages.
The agent's prompt says "Every item you get has already passed the appro..." before the frame cuts off. That places the approval check in n8n nodes ahead of the agent, so the model does not decide who is allowed to teach it.
What Slack permissions does the bot need?
The description says "the bot has four permissions and can't read private channels or DMs." The video's scope list is not visible in the frames reviewed. Slack's reaction_added documentation lists reactions:read as the required scope for that event and says it is delivered for content the user can see. Whether the bot is blind to private channels depends on which channel-history scopes you grant, so check that in your own app configuration.
How does it avoid making things up?
The description says the assistant must "bring a quote copied word for word from a page it opened, and n8n checks that the quote is really on that page before the answer goes out." Links "come from the map, never from the AI."
Two answer paths appear on screen:
- Answered. Asked "Who is building the Northgate site, and can they launch it on a Friday?", Brain names Jordan Ellis, says the rules forbid Friday launches, gives a launch date of Thursday 2026-11-19, and cites two pages: "Northgate Property Management" and "How We Do Things".
- Refused. Asked about the refund policy for a project cancelled halfway, Brain says "That's not in the brain yet, so I won't guess. I've logged it to Gaps for Priya."
The frames do not show the quote-matching node, and they do not show a case where a bad quote was blocked. A card captioned "Claims vs real edits" shows a "CLAUDE SAYS" box reading "Changed the price on Shopify store", which suggests the workflow compares what the model claims it changed with the real document edits. The implementation is not shown. Treat the no-invented-quotes guarantee as a design goal until you can test it.
Is the demo data real?
No. The description says Harborline is a company "we set up for this." Jordan Ellis, Northgate, the launch date (three weeks after the video was posted) and the description's "$24,000, was $22,000 until 2026-10-27" example are all demo data, not customer results.
How far does this design scale?
The brain uses an Index page that lists every page. The agent reads the index and then opens only the relevant pages. The description admits the limit: "Brain reads the map every time. Past a few hundred pages, you'd add a search step." That threshold is the author's estimate.
The description also lists a Monday report covering conflicting facts, sections unreviewed for 90 days and open questions. A loop diagram shows "Monday report" next to n8n, but no report appears on screen.
Can you get the template?
Not from the video. The description says "I'm dropping this system inside my community soon" and points to "the link in my profile". There is no URL in the description, so the build is not available beyond what the frames show.
Bottom line
The design is worth copying: approvals checked outside the model, answers that must quote a real page, and an explicit "I won't guess" path that logs gaps for a person. The demo runs on a made-up agency, and the quote check, Slack permission set and Monday report are claims in the description that the frames do not show working. The author's own advice is to start small.
Sources
- reaction_added event, Slack developer docs: required
reactions:readscope and delivery rules. - Anthropic Chat Model node, n8n docs: using Claude chat models with n8n agents.
- TikTok post by @pro.glitch: the video and description reviewed here.
Published October 28, 2026. Based on a TikTok by @pro.glitch. Full video notes (markdown)