Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.clarityq.ai/llms.txt

Use this file to discover all available pages before exploring further.

Once your Slack workspace is connected, the ClarityQ bot can post task deliveries to channels and answer questions in DMs and in any channel it’s been invited to. This page covers the day-to-day interactions.

​
Receiving Task Deliveries

When a task runs, its results are posted to the Slack channel you selected when scheduling it. Each delivery includes:
  • The product name and a header showing which task ran.
  • The task’s output, formatted as Slack-friendly Markdown — tables come through as code blocks, and larger outputs land as file attachments.
  • A View Chat button linking back to the conversation in ClarityQ.
Each scheduled run is a separate top-level message in the channel — replying in-thread doesn’t trigger a new agent run. Use View Chat to continue the conversation in ClarityQ.

​
Asking ClarityQ in Slack

If your Slack integration was originally connected only for task deliveries, an admin will need to reconnect the app from Settings → Integrations to grant the additional permissions required for asking questions in Slack.
You can talk to ClarityQ without leaving Slack in two ways.

​
@Mention in a channel

Mention the bot in any channel it’s a member of, with your question as the text — for example, @ClarityQ what's revenue by region this quarter?. The bot acknowledges in a thread and updates the same message once the answer is ready. Each Slack thread maps to a single ClarityQ chat.

​
Direct message the bot

DM the bot the same way. The conversation lives in the DM thread; the agent responds inline.

​
Product resolution

When you ask a question in Slack, ClarityQ needs to know which product to query. It resolves this automatically:
  • Single product — If you only have access to one product, it’s used automatically.
  • Multiple products — ClarityQ uses your default product, which is initially set based on your most-used product in ClarityQ. You can change it at any time with the /clarityq set-default-product command.
  • Explicit selection — You can specify a product by wrapping its name in brackets in your message, for example: @ClarityQ [MyProduct] what was revenue last week?
  • Disambiguation — If ClarityQ can’t determine which product to use, it shows buttons letting you pick one.
Once a conversation thread is started on a product, all follow-up messages in that thread stay on the same product — you can’t switch products mid-conversation.
ClarityQ does not check whether everyone in a Slack channel has access to the product being queried. Anyone in the channel can see the bot’s answers, even if they don’t have a ClarityQ account or access to that product (they won’t be able to open the View Chat link or continue the conversation in ClarityQ). Be mindful of which channels you ask questions in if your data is sensitive.

​
How Slack chats work

In both cases, the bot’s reply includes a View Chat button that opens the conversation in ClarityQ. A few important things to know about Slack chats:
  • One owner per thread — Only the user who started the thread can continue the conversation. Messages from other users in the same thread are ignored by the bot.
  • Chat history — The conversation is created in the starting user’s chat history in ClarityQ, marked with a Slack icon so you can find it easily.
  • Opening in ClarityQ ends the Slack thread — Once you open the chat in ClarityQ (via the link or from your chat history), the Slack thread stops accepting new messages. From that point on, the conversation can only be continued in Ask Anything.
  • Other users in the channel — Other users can click the View Chat link to see a read-only version of the conversation. They can fork the chat and continue it independently in their own ClarityQ account.

​
Slash Commands

Run these from any channel or DM in Slack:
CommandWhat it does
/clarityq helpShow all available commands.
/clarityq connectLink your Slack identity to your ClarityQ account so the bot recognises you and ties chats back to your ClarityQ user.
/clarityq productsList the ClarityQ products available in this Slack workspace.
/clarityq set-default-product <product>Choose which product the bot uses when you @mention it without context.
If your Slack email matches the email you used to sign in to ClarityQ, the bot recognizes you automatically — no setup needed. If your Slack email is different, run /clarityq connect once to link your Slack identity to your ClarityQ account. Until linked, the bot won’t be able to answer your questions.

​
When Things Go Wrong

A few common failure modes:
  • The bot was removed from a channel. Task deliveries to that channel start failing silently. Re-invite the bot with /invite @ClarityQ and the next delivery resumes.
  • The Slack token expired or new scopes are required. Posts stop and the Integrations page shows a reconnect prompt. Click Reconnect to re-run OAuth.
  • The bot doesn’t recognize you. If your Slack email differs from your ClarityQ login email, run /clarityq connect to link your identity. Without it, chats can’t be attributed to your ClarityQ account.