Zentrik + Slack

• 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.

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.

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.

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.

• @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.
• The first write workflows are thread capture and review-gated idea or opportunity creation. Broader edits and deletes are not supported from Slack yet.
• Capture product-relevant customer context. Avoid capturing private conversation or internal noise that does not belong in the shared product record.

• 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.

• 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.