Does Watari read my Slack messages?

No. Watari is outbound-only. The five requested bot scopes (chat:write, chat:write.public, channels:read, channels:join, groups:read) cover posting notifications and listing channels for the channel picker. No message-history or search scope is requested, so reading workspace messages is not technically possible with the granted permissions.

What notifications does Watari post?

Bug detected (a customer-reported bug extracted and mapped to the responsible file and function), draft PR opened, fix shipped with customer-facing RCA published, duplicate-cluster growth (more customers reported the same bug), and feature-request signals. Every type can be enabled or disabled per organization in Settings → Notifications.

Can Watari post to a private channel?

Yes. Invite @Watari to the private channel in Slack first, then select it in the channel picker. The groups:read scope only lets Watari list private channels it has already been invited to — it cannot see other private channels.

What happens after I click Allow on the Slack consent screen?

Slack redirects you back to Watari’s Settings → Integrations page with the Slack card marked Connected. Next step is picking a notification channel; after that, notifications flow automatically. If anything fails mid-install, the same page shows the error and a retry button.

Why does the consent screen say "App is not approved by Slack"?

That banner appears on every Slack app distributed outside the Slack Marketplace and does not affect installation or functionality. Watari’s Marketplace listing is in progress — Slack requires an app to be live on several active workspaces before it reviews a listing. The OAuth flow, scopes, and security posture are identical either way.

How do I disconnect, and what data does Watari keep?

Click Disconnect on the Slack card in Settings → Integrations — Watari deletes the workspace token and stops posting immediately. While connected, Watari stores only the AES-256-GCM-encrypted bot token and your selected channel ID, isolated per organization via Postgres row-level security. No Slack message content is ever stored, because none is ever read.

Slack Marketplace · Developer Tools

Watari for Slack

Q: Does the Slack integration cost extra?

No. Slack notifications are bundled with every plan and are never metered. You pay only per Mapped Bug — a structured bug paired with the file and function responsible, both at ≥ 0.7 confidence. PR drafts, customer-facing RCA, and Jira / GitHub Issues sync are bundled the same way.

Bug, PR, and RCA notifications — where your team already works.

Watari turns customer support tickets into bugs mapped to the file and function responsible, drafts the fix PR, and tells the customer when it ships. The Slack integration is how your team hears about each step — outbound-only notifications in a channel you pick. Watari never reads your Slack messages.

Add Watari to Slack See pricing

Installation starts from your Watari dashboard — sign up free, then Settings → Integrations → Slack. Already a customer? Connect Slack now. By installing you agree to our privacy policy and terms.

Trial: 14 days · 10 Mapped Bugs
Reads messages: Never
Setup: OAuth · 2 minutes
Slack add-on cost: None — bundled

What is Watari for Slack?

Watari for Slack is an outbound-only notification integration. When Watari extracts a bug from a customer support ticket and maps it to the responsible file and function at ≥ 0.7 confidence, it posts to a Slack channel you choose — and posts again when the draft PR opens and when the fix ships with a customer-facing RCA. It requests no message-reading scopes.

Why support and engineering teams connect Watari to Slack

Outbound-only by design

Watari posts notifications; it never reads a single message. No message-history scopes are requested — the consent screen shows exactly five bot scopes, all of them about posting and picking a channel.

Bug alerts with real engineering context

When a customer-reported bug clears the dual ≥ 0.7 confidence gate, the Slack notification carries severity, the mapped file and function, and a link to the full structured record — not a bare ticket URL.

PR lifecycle in the channel

The channel hears when the draft pull request opens for a mapped bug, so reviewers can jump straight to the diff without watching GitHub.

Closed-loop RCA alerts

When the fix lands in a successful production deploy and the customer-facing RCA posts back to the original ticket, your team sees it in Slack — the loop closes in front of everyone.

Duplicate-cluster alerts

When more customers report the same underlying bug, Watari clusters them and notifies the channel that an existing bug grew — one thread of truth instead of ten parallel escalations.

Self-healing channel health

If the configured channel is archived or the bot is removed, Watari detects it, marks the integration in Settings with a clear fix-it message, and automatically re-checks so notifications resume without manual babysitting.

How to install Watari in your Slack workspace

Create your Watari account
Sign up at watari.ai — the 14-day free trial includes 10 Mapped Bugs and needs no credit card. Connect your support tool (Zendesk or Intercom) and your GitHub repository first; Slack is the notification layer on top.
Connect Slack from Settings → Integrations
In the Watari dashboard, open Settings → Integrations and click Connect on the Slack card. You are redirected to Slack’s standard consent screen, which lists the five bot scopes Watari requests — all outbound posting and channel-listing scopes, none that read messages.
Approve the install in your workspace
Click Allow on Slack’s consent screen. Slack redirects you straight back to Watari’s integration settings with the Slack card marked Connected — that is your confirmation the install succeeded.
Pick your notification channel
Choose a channel from the picker (public channels list automatically; for a private channel, invite @Watari first and it appears). Watari joins the selected public channel on its own — no manual /invite needed.
Notifications start flowing
From the next qualifying ticket onward, the channel hears when a bug is extracted and mapped to code, when the draft PR opens, and when the fix ships with a customer-facing RCA. Each notification type can be toggled per organization in Settings → Notifications.

After you install

A successful install drops you back on Watari’s Settings → Integrations page with the Slack card marked Connected. From there:

Pick a channel. Public channels appear automatically; Watari joins your selection on its own. For a private channel, invite @Watari in Slack first and it shows up in the picker.
Choose notification types. Bug detected, draft PR opened, RCA published, and cluster-growth alerts are each toggleable per organization in Settings → Notifications.
Watch the first notification land. The next support ticket that clears the ≥ 0.7 confidence gates posts to your channel with severity, the mapped file and function, and a link to the full bug record.
Disconnect any time. One click on the Slack card removes the token and stops all posting immediately.

Exactly what Watari can do in your workspace

Watari requests five bot scopes — the minimum needed to post notifications and power the channel picker. The consent screen you approve lists each one. No user scopes, no message-history scopes, no admin scopes.

Post: chat:write + chat:write.public — send notification messages to your selected channel, including public channels the bot hasn’t been invited to (covers edge cases where auto-join fails).
List channels: channels:read + groups:read — populate the channel picker with public channels and the private channels the bot is already a member of. Channel names and IDs only — never message content.
Join: channels:join — automatically join the public channel you pick, so there is no manual /invite step.
Store: The bot token (AES-256-GCM encrypted before persistence) and your selected channel ID. Tenant data is isolated via Postgres row-level security on every table. No Slack message content is stored — none is ever read.

Pricing

Slack notifications are bundled with every plan — never metered. You only pay when Watari delivers a Mapped Bug: a structured bug paired with the file and function responsible, both at ≥ 0.7 confidence. PR drafts, customer-facing RCA, and Jira / GitHub Issues sync are bundled the same way.

Starter

$400/mo

20 Mapped Bugs included · $25/bug on-demand

For small support teams routing their first Mapped Bugs.

Growth

$900/mo

60 Mapped Bugs included · $20/bug on-demand

For teams running customer support at production volume.

Scale

$1,800/mo

150 Mapped Bugs included · $15/bug on-demand

For multi-repo SaaS with a dedicated support function.

Indian buyers (with GSTIN) are billed in INR; everyone else in USD. 14-day free trial · 10 Mapped Bugs included · no credit card required. Annual billing saves 17%. Full plan comparison at watari.ai/pricing.

Security & privacy

Outbound-only — no message-reading scopes requested.
Bot token AES-256-GCM encrypted at rest.
Postgres row-level security on every tenant-scoped table.
Your tickets and code never train any model.
OAuth state HMAC-signed against forgery on every install.
Full security posture at watari.ai/security · privacy details at watari.ai/legal/privacy.

Frequently asked questions

Your next support ticket arrives as a draft PR.

Connect Zendesk or Intercom, install the GitHub App. Tickets land mapped to the file, function, and line — ready for your reviewer to take over.

Start free trial

Trial length: 14 days
Bugs included: 10 Mapped
Card required: No
Mismapped credit: 7 days
Cancel: Any time

You only pay when we know what to change.