Guru Slack Integration: Set It Up and Keep the Knowledge Behind It Current

The Guru Slack integration lets your team surface verified knowledge cards inside Slack without opening a separate browser tab. A teammate asks a question, the Guru bot suggests a relevant card, and the answer is right there in the conversation. The part the integration does not cover is what happens after the answer: the follow-up decision, the task that needs tracking, the rule the team agreed to follow. Tools like fenbs hold that active work context alongside the stable reference knowledge Guru provides.

This guide covers setting up the integration, using the Guru bot in channels, keeping cards current, and capturing the decisions and tasks that come out of those conversations.

What the Guru Slack integration does

Once installed, the Guru Slack app gives your team two main capabilities. First, anyone can search the Guru knowledge base from Slack using the /guru command or by mentioning @Guru. The bot returns matching cards inline without leaving the conversation. Second, users can save a Slack message directly as a new Guru card using the message actions menu, which makes it easy to capture useful answers before they get buried in scroll.

Guru also watches for questions in channels you configure and proactively suggests a card if one matches. This works best in topic-focused channels such as onboarding, support, or engineering FAQs, where the pattern of questions is predictable. In general team channels, suggestions are harder to tune.

Check Guru's Slack integration documentation↗ (opens in a new tab) for the current setup steps and any updated features. The Guru app has changed between versions and specific steps may differ from what older guides describe.

How to set up the Guru Slack integration

1. Go to your Guru workspace settings and find the Integrations section.
2. Select Slack and follow the authorization flow to connect your Slack workspace.
3. Choose which Slack channels Guru should monitor for question suggestions.
4. In Slack, the Guru app will appear in your Apps list. Announce the /guru command to your team and explain what the bot covers.
5. Test by asking a question in a configured channel and verifying the bot suggests a relevant card.

Getting useful answers from Guru in Slack

The /guru command searches your knowledge base and returns the top matching cards. Results are only as good as the cards behind them. A well-written card answers one specific question, has a clear owner, and is short enough to read in under a minute.

If searches return the wrong cards or no results, the gap is usually in the card content rather than in the integration. Check whether a card exists for the question being asked, whether its title and tags are searchable, and whether the content is still accurate.

Keeping Guru cards current

Every Guru card has an owner responsible for verifying it on a set schedule. When a card expires its verification interval without being confirmed, Guru flags it as potentially outdated. Build card review into your process: when a policy, a tool, or a procedure changes, update the relevant cards immediately rather than waiting for the flag.

Assign card ownership when creating the card, not afterward. Without an owner, outdated cards go unnoticed and produce confidently wrong answers. Use Guru's collections feature to assign ownership by team so no individual holds more cards than they can realistically maintain.

For the relationship between Guru cards and active work state, see the related article on Guru in Slack: workflow. Stable reference knowledge belongs in Guru; current project state belongs in an active work record.

Capturing decisions and tasks from Slack conversations

Slack conversations often produce follow-up work: a question gets answered, someone raises a concern, the team agrees to handle something differently going forward. Those outcomes disappear into scroll within hours. Saving a message as a Guru card helps for facts that should become permanent reference. For decisions and tasks, a card is the wrong format.

A decision the team made in Slack needs to be recorded where the next person can find it, act on it, and see who made it. A task that came up in a question thread needs an owner, a plan, and a place in the work queue. Slack and Guru are not designed for either of those.

How to do this with fenbs

1. Create a free account and add a project for the team work that generates Slack conversations.
2. When a conversation produces a decision, add it to Decisions and rules in fenbs. Record who decided, what was decided, and why.
3. When a conversation produces a task, add it to the project board with a plan and an owner.
4. Connect your AI assistant over MCP from Integrations. Ask it to read the project context before team work sessions so it starts from the current decisions and tasks.
5. Use Guru for stable reference knowledge and fenbs for active work context. Point the team to the right source for each type of question.

fenbs does not replace Guru. The two tools cover different needs: Guru for what is always true, fenbs for what is true right now. For integrating Guru with other tools, see Guru Google Drive integration.