--- title: "Zentrik + Slack" canonical_url: https://zentrik.ai/docs/integrations/slack markdown_url: https://zentrik.ai/docs/integrations/slack.md category: "Integrations" learning_track: null last_reviewed: 2026-07-22 --- # Zentrik + Slack Keep product work moving from the conversation: connect evidence, preserve useful threads, and prepare the next move for review. ## Overview @Zentrik is a shared teammate for a Zentrik workspace. Mention it in a channel or send it a direct message to connect a live conversation with existing product context, preserve a useful thread as a Discovery signal, or prepare an idea or opportunity for review. Answers are grounded in the connected Zentrik workspace. Creating an idea or opportunity always requires a person to choose **Create** in Slack; a draft alone does not change the product record. ## Before you connect - You need permission to install apps in the Slack workspace, or an admin who can approve the install. - Decide which Zentrik workspace the Slack workspace should use. One Slack workspace connects to one Zentrik workspace per environment. - The installer becomes the default acting member. @Zentrik follows that member's Zentrik permissions while recording the actual Slack requester in its audit trail. ## Connect Slack 1. In Zentrik, open **Settings → Integrations → Slack**. 2. Choose **Add to Slack**. 3. Review the Slack permissions and approve the workspace. 4. Return to Zentrik and confirm the connection shows **Connected**. 5. Invite @Zentrik to a test channel, mention it, and ask a small question about the connected workspace. Reconnect from the same page if the app is removed, its token is revoked, or Zentrik reports that authorization needs attention. ## Share with your team After Slack is connected, share this note in the channel where your team will use Zentrik. The formatted `@Zentrik` is intentional so the app is not mentioned until someone is ready to demonstrate the flow. ```text *How to use `@Zentrik` in this channel* `@Zentrik` connects our conversations to the product context, customer evidence, and existing product work in Zentrik. Mention it when you want to: - Find existing evidence: `@Zentrik what do we already know about onboarding friction?` - Save useful context: `@Zentrik capture this thread as a signal. It describes a customer request.` - Prepare product work: `@Zentrik draft an idea from this discussion for [target user and problem].` - Check existing work: `@Zentrik do we already have an idea or initiative for this?` When bringing in new context, include the customer or account, product area, source or date, and whether it is a request, bug, objection, workflow, or decision. `@Zentrik` shows the evidence behind its answer and asks for confirmation before creating a new idea or opportunity. The formatted `@Zentrik` is intentional. It keeps this presentation message from invoking the app. When you are ready to demonstrate the flow, replace it with the Zentrik app mention from Slack's suggestions in a new message. For a first demo, try: `@Zentrik what product context do we already have for [product or problem]?` ``` To demonstrate a sample, copy one into a new Slack message, replace its formatted `@Zentrik` with the app mention from Slack's suggestions, and send it. Keep the examples in a thread when the question depends on earlier messages. ## What to try first Choose the outcome you need, then copy that prompt into a channel where @Zentrik has been invited or use it in a direct message: - **Find customer evidence:** `@Zentrik what customer evidence mentions onboarding friction?` - **Check for existing work:** `@Zentrik do we already have an idea for this?` - **Save a useful discussion:** `@Zentrik capture this thread as a signal` - **Prepare an idea for review:** `@Zentrik create an idea from this discussion` - **Ask what to build next:** `@Zentrik what should we build next based on recent evidence?` - **Review a specific idea:** `@Zentrik summarize the evidence around IDEA-42` Replace the example topic or record id with something from your connected Zentrik workspace. ## Use @Zentrik **Ask from product context** Mention @Zentrik in a channel or message it directly. Ask a focused question such as “What evidence do we have about onboarding friction?” or reference a Zentrik record such as **IDEA-42**. **Capture evidence** Ask @Zentrik to capture the useful message or thread. It creates a Discovery signal with the Slack context needed for later synthesis. **Prepare a product next step** Ask it to draft an idea or opportunity. Review the proposed title and description, then choose **Create** or **Cancel** in Slack. Nothing is persisted until a person confirms it. ## Beta limits - @Zentrik responds to explicit mentions and direct messages. It does not continuously monitor channels. - It can only read conversations in channels where the app has been invited. - Answers come from the connected Zentrik workspace. Sparse workspace evidence will produce limited answers. - Slack supports thread capture and review-gated idea or opportunity creation. Use Zentrik for other edits and deletions. - Capture product-relevant customer context. Avoid capturing private conversation or internal noise that does not belong in the shared product record. ## Best practices - Ask one product question at a time. - Name the relevant product, account, or customer when it would remove ambiguity. - Use a thread when the request depends on several messages of context. - When capturing a thread, say what it represents: a bug, request, objection, workflow, or decision. - For idea drafts, include the target user, their problem, and the desired outcome. - Review the proposed title and description before choosing **Create**. Choose **Cancel** if the product record needs more work. ## Access and control - Zentrik stores the Slack bot authorization server-side, not individual Slack passwords. - @Zentrik can only answer from Zentrik data the acting workspace member is allowed to access. - The bot needs to be present in a channel before it can read and answer there. - Thread capture and confirmed creates are recorded so workspace admins can trace what happened. - Disconnecting Slack stops new access. Product records already created in Zentrik remain until your team removes them through normal product controls. ## Troubleshooting ### @Zentrik does not answer in a channel Invite the app to the channel and mention @Zentrik explicitly. Check the Slack integration in Zentrik; if its status is unclear but @Zentrik replies in a test channel, the connection is active. ### Slack requires administrator approval Ask a Slack administrator to approve the Zentrik app, then restart the connection from **Settings → Integrations → Slack**. ### @Zentrik asks me to paste a thread Paste the thread text together with what you want Zentrik to do. If it repeats, confirm the app is present in the channel and check **Settings → Integrations → Slack**. ### Expected product context is missing Confirm Slack is connected to the intended Zentrik workspace and that the acting member has access to the relevant records. ## Related guides - [Zentrik + Jira](https://zentrik.ai/docs/integrations/jira) - [Zentrik + GitHub](https://zentrik.ai/docs/integrations/github) - [Zentrik + Linear](https://zentrik.ai/docs/integrations/linear)