Answer Slack questions from every tool you connect

By General Input

When someone asks a question in Slack, the bot searches your docs, tickets, drive, and email, then replies with a source-backed answer.

Integrations

  • Slack
  • Notion
  • Google Drive
  • Gmail
  • Linear
  • Jira
  • Asana
  • Box
  • Dropbox
  • Microsoft SharePoint
  • Microsoft Teams
  • Microsoft Outlook
  • Monday.com
  • HubSpot

Type

Agentic Task

Categories

  • Operations
  • Personal Productivity

I want a knowledge search agent that lives in Slack and answers team questions using every tool we have connected.

Trigger: whenever someone @-mentions the bot in any Slack channel it has been invited to, or sends it a direct message. The text of that message is the question.

What the agent should do, in order:

1. Read the user's question from the Slack message. If the question is unclear, ask one short clarifying question in-thread and stop.

2. Plan a short multi-source search strategy. Pick which connected sources are most likely to contain the answer and what query to send to each. Skip any source that is not connected.

3. Run the searches in parallel against the relevant sources. Treat all of these as candidates: past Slack messages and threads, Notion pages, Google Drive files, Gmail messages, Linear issues, Jira issues, Asana tasks, Microsoft SharePoint drive items, Dropbox files, Box content, Microsoft Teams channel messages, Microsoft Outlook messages, Monday.com items, and HubSpot contacts and notes.

4. For the top few hits per source, fetch the underlying content so the agent can actually read it: the Notion page body, the Drive file content, the email body, the issue or task description, the SharePoint or Dropbox or Box file, the Teams or Outlook message body. Do not answer from titles alone.

5. Synthesize one clear answer that is grounded only in what was found. If sources disagree, call that out. If the search came up empty or weak, say so honestly rather than guessing.

6. Post the answer as a reply in the same Slack thread where the bot was mentioned. End every answer with a short Sources list of clickable links to the exact pages, files, tickets, or messages used.

Rules to bake in: never fabricate, never answer from a source that was not actually retrieved, keep the default answer under about 200 words with citations stacked at the end, and treat any source the user has not connected as silently unavailable.

Optional second mode the user can turn on later: a weekly digest, posted on a schedule into a chosen Slack channel, summarizing the questions people asked that week, the answers given, and which tools held the answers most often. Build the question-answering trigger first and leave the digest as a clean follow-on.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredTurn Mailjet email clicks into ranked HubSpot follow-upsiMessage campaign console with pre-flight checks and delivery boardChat quality review board for LiveChat support leadsA searchable RFP answer library your bid team drafts fromSee which target accounts just started advertising on LinkedInAccount health board that puts product usage next to your CRMLook up a customer's full chat history mid conversationChase the paperwork every new client and vendor still owes