Tag Fabric in any Slack or Discord channel and it does anything you would do inside the app. Ask questions, dispatch agents, trigger actions, and access your entire workspace from a single @mention.

Your workspace, inside the conversation.

Ask a question, get an answer.
@mention Fabric in any channel and ask a question. It searches across your entire workspace, every note, file, transcribed recording, and piece of connected content, and answers with cited sources. The same AI assistant you use inside the app, available where your team is already talking.

Dispatch an agent.
Tell Fabric to research a topic, summarise a folder, monitor a channel, or run any task you would normally set up as a background agent. Dispatch it with a message and the results appear in your workspace when they are ready.

Trigger actions.
Create a task, update a document, save a bookmark, pull data from a connected app, or run any action Fabric supports. Your workspace and all its connections are accessible from the @mention.

No app switching. No context switching.

Stay in the conversation.
The most disruptive part of using a tool is leaving the conversation to go use it. Someone asks a question in Slack. You open Fabric, search for the answer, copy it, switch back to Slack, and paste it. With Fabric Tag, you type @Fabric and the answer appears in the channel where the question was asked.

Everyone sees the answer.
When Fabric responds in a channel, the whole team sees the answer. There is no private lookup that stays in one person's head. The information surfaces where the conversation is happening, which means everyone benefits from the same context at the same time.

Threaded responses.
Fabric responds in threads to keep channels clean. Follow-up questions and additional context stay organized in the same thread. The conversation with Fabric flows naturally alongside the team's own discussion.

Why answers should live where questions are asked.

Most knowledge management tools have the same problem. The knowledge is in one place and the conversations are in another. Your team discusses a topic in Slack, someone needs a fact or a document, and they have to leave the conversation, open a different app, find what they need, and bring it back. This friction is small for a single lookup but it compounds across dozens of questions a day across an entire team. Some questions never get answered because the effort of switching apps is not worth it in the moment.

Fabric Tag removes that friction entirely. Your workspace, your AI assistant, your agents, and all your connected apps are accessible from the place where questions naturally arise. A question in Slack gets answered in Slack, with sources from your workspace. A request to create a task or update a doc happens without anyone opening a browser tab. The knowledge flows to where the team is working rather than requiring the team to go to where the knowledge is stored.

More than a chatbot in your channel.

Fabric Tag is not a simple Q&A bot. It has the full capabilities of your Fabric workspace behind it. You can ask it to search across all your content, including files from Google Drive, Dropbox, Notion, and every other connected source. You can dispatch background agents to handle tasks that take longer than a simple search. You can trigger actions that modify your workspace, from creating tasks and notes to moving files and applying tags.

For teams that have invested in building a rich Fabric workspace with self-writing docs, connections, and organized content, Fabric Tag makes all of that investment accessible from the tools people spend most of their day in. The workspace becomes a service the team can call on at any moment, rather than an app they have to remember to visit.

Multiplayer by default.

When a single person uses the AI assistant inside Fabric, they get an answer for themselves. When someone uses Fabric Tag in a channel, the entire channel gets the answer. This changes the dynamics of how teams access institutional knowledge. Instead of one person knowing where to find something and relaying it to others, the knowledge surfaces publicly. New team members see how questions are answered and learn what the workspace contains. The @mention and the response become part of the channel's history, searchable and referenceable later.

For startups building a culture of knowledge sharing, agencies coordinating across accounts, and remote teams that rely on asynchronous communication, this public knowledge surfacing is as valuable as the answers themselves.

Use cases

Team Q&A
Someone asks a question in Slack about a past decision, a client, or a project. Instead of pinging a colleague or digging through files, they @mention Fabric and the answer appears in the thread with citations from your decision log, project docs, or meeting notes.

Agent dispatch
Need a research summary, a competitive analysis, or a weekly digest? Dispatch an agent from Slack or Discord and the results land in your workspace. Useful for tasks that take longer than a quick search.

Quick actions
Create a task from a Slack message. Save a link as a bookmark. Update a note with new information. Fabric Tag turns any channel message into a workspace action without switching apps.

Client and sales context
A rep asks @Fabric about a client's history before a call. The answer draws from the client relationship tracker and sales knowledge base, surfacing deal context, past meeting outcomes, and outstanding items. See how Fabric supports CRM.

Onboarding support
New hires @mention Fabric in any channel to ask questions about processes, tools, and team context. The answers come from onboarding docs and the broader workspace, reducing the number of questions that go to busy colleagues. See how Fabric supports onboarding.

Perfect for

Remote and distributed teams
When your team communicates primarily through Slack or Discord, putting your knowledge base one @mention away means information flows at the speed of conversation. Learn more about Fabric for teams.

Startups
Fast-moving teams need fast answers. Fabric Tag gives everyone on the team instant access to everything the company knows without leaving the conversation they are already in. Learn more about Fabric for startups.

Agencies
Account teams working across multiple client channels can pull client context, project history, and deliverable status into any conversation with a single @mention. Learn more about Fabric for agencies.

Engineering teams
Ask Fabric about architecture decisions, deployment history, or system behavior directly in your engineering channels. The answers draw from engineering docs, PRs, and technical discussions. Learn more about Fabric for engineering teams.

Works seamlessly with other features.

AI assistant
Fabric Tag uses the same AI assistant that powers the Fabric app. The same search capabilities, the same content access, the same citation quality.

Background agents
Dispatch agents directly from Slack or Discord. Research tasks, monitoring jobs, and recurring workflows are all accessible from an @mention.

Self-writing docs
Answers from Fabric Tag draw from your self-writing documentation, including decision logs, engineering docs, product docs, and client trackers.

Connections
Fabric Tag can access content from all your connected apps. Ask about a file in Google Drive, reference a Notion page, or search across Gmail, all from a Slack message.

FAQ

How do I set up Fabric Tag?
Add the Fabric bot to your Slack workspace or Discord server through the setup wizard. Choose which channels Fabric can respond in, and your team can start @mentioning immediately. See the connections marketplace for setup details.

Does Fabric respond to every message in a channel?
No. Fabric only responds when someone @mentions it. It does not read or respond to general conversation. If you want Fabric to monitor channels for documentation purposes, that is a separate capability through self-writing docs.

What can I ask Fabric Tag?
Anything you would ask the AI assistant inside the app. Search across your workspace, ask questions about your content, request summaries, dispatch agents, create tasks and notes, and trigger actions across connected apps.

Can I dispatch agents from Slack?
Yes. Tell Fabric to research a topic, summarise content, or run any task that a background agent can handle. The results are delivered to your Fabric workspace.

Can I create tasks and notes from Slack?
Yes. Ask Fabric to create a task, save a bookmark, or create a note directly from a Slack or Discord message. The item appears in your workspace immediately.

Does Fabric Tag work in private channels and DMs?
Configuration depends on how you set up the bot in your workspace. You can control which channels Fabric has access to and where it can respond.

Can everyone on my team use Fabric Tag?
Yes. Anyone in the Slack workspace or Discord server where Fabric is installed can @mention it. Responses are based on the workspace content that the team has access to, respecting existing permissions.

Does Fabric Tag cite its sources?
Yes. Responses include citations to the specific files, notes, documents, or recordings that the answer draws from. Team members can click through to the source in Fabric for more context.

Is this available on all plans?
Fabric Tag is available on Team plans. See team pricing for details.

How is this different from a Slack bot that searches a wiki?
Most Slack search bots perform keyword lookups against a static knowledge base. Fabric Tag has the full AI assistant behind it with semantic search across all your content, the ability to dispatch agents, and the ability to trigger actions in your workspace and connected apps. It is not a search bot. It is your entire workspace, accessible from an @mention.