Integrating Sazabi with Slack

Learn how to integrate Sazabi with Slack so you can surface production insights and receive issue notifications without leaving your team's communication hub. The integration also lets Slackbot access the Sazabi MCP server, so your team can ask Slackbot to discover and use Sazabi tools directly in Slack.

About the Sazabi integration for Slack

The Sazabi integration for Slack gives your team visibility into production systems directly in Slack channels. You can investigate issues, receive notifications, and collaborate on incidents without switching applications.

With the Sazabi integration for Slack, you can:

• Get issue notifications in Slack channels, with inline actions to mute, unmute, or resolve them.
• Chat with Slackbot and let it use the Sazabi MCP server to query logs, check issues, inspect projects, and find available Sazabi operations.
• Ask Sazabi questions by mentioning @Sazabi in any channel to debug production issues in natural language.
• DM Sazabi directly for a continuous conversation about your systems.
• Give your team more context when you share links to Sazabi threads and issues in Slack.

Prerequisites

Before you connect Slack, make sure you have:

• A Sazabi account. Request access at sazabi.com
• A Slack workspace where you have permission to install apps.
• A paid Slack workspace plan, which is required to use the Sazabi integration for Slack.

Installation

Connecting your Sazabi account to the Sazabi app in Slack

Sazabi matches your Slack identity to your Sazabi account by email address. As long as the email on your Slack profile matches the email on your Sazabi account, you are connected automatically.

If the email addresses do not match, update one of them before Sazabi can respond to your messages.

Mentioning @Sazabi in Slack

Once Sazabi has been invited to a channel, any workspace member can ask it questions by mentioning it directly.

@Sazabi why are checkout errors elevated right now?
@Sazabi how many 5xx responses did the payments service return in the last hour?
@Sazabi show me the slowest database queries from today

Sazabi adds a reaction to acknowledge the message, then replies in-thread with a plain-language answer based on your connected logs, traces, and metrics. You can continue the conversation by replying in that thread.

Automatic replies and reactions

A single opt-in toggle under Settings > Integrations > Slack controls whether the Sazabi Slackbot automatically follows up in threads it is part of. When enabled, the Slackbot automatically replies to follow-up messages in threads it was mentioned in (without needing to be re-tagged) and adds an acknowledgement reaction to messages it processes. Replies are gated by a relevance check, so it only responds when the follow-up is directed at it. This is off by default.

You can also DM Sazabi directly. The entire DM history is treated as a continuous conversation, so you do not need to re-establish context between messages.

Receiving issue notifications in Slack

Issue notification channels are configured per project under Settings > Notifications. Enable the Slack channel for the project and select one or more Slack channels to receive its issue notifications. Each message includes a description of what was detected, the root cause analysis, suggested remediation, and a link to the full investigation in the Sazabi dashboard.

You can act on an open issue directly from Slack using the inline buttons:

• Fix: Ask Sazabi to start working on a fix for the issue.
• Mute: Suppress future notifications for this issue.
• Unmute: Re-enable notifications for a muted issue (shown in place of Mute once an issue is muted).
• Resolve: Mark the issue as resolved.
• Ignore: Dismiss the issue as not requiring a fix.

Issue cards also include a Submit Feedback action so you can tell Sazabi whether the issue was accurate and actionable.

Status changes are reflected immediately in both Slack and the Sazabi dashboard.

Sharing Sazabi links in Slack

When you share a link to a Sazabi thread or issue in any Slack channel, the app automatically unfurls it with a rich preview. This gives your teammates context without needing to open the dashboard.

Connecting your personal Slack account

Email matching links your Slack identity to Sazabi so the bot can respond to you. Separately, each member can connect their personal Slack account to unlock direct-message notifications and let Sazabi work with the Slack context you already have access to.

Connect your account under Settings > Connected accounts in the Sazabi dashboard. This authorizes a read-only Slack user token — Sazabi is granted no write or admin scopes, so it cannot post messages, change settings, or modify anything in your workspace. With it connected, Sazabi can:

• Search and read Slack on your behalf, grounding investigations in the channels, direct messages, and files your account can already see.
• Reach you with direct-message notifications. When your organization also has the organization-level Slack integration installed, Sazabi can open a DM with your Slack user and send notifications — for example when an issue is triggered or resolved. You control which notification types reach you from your notification preferences.

Chatting with Slackbot through the Sazabi MCP server

After the Slack workspace is connected and your Slack identity is linked to your Sazabi account, Slackbot can use Sazabi through the Model Context Protocol (MCP). This gives Slackbot access to Sazabi in the same Slack conversation where your team already works.

For example, you can ask Slackbot:

Can you use the Sazabi MCP server to list my current projects?
Use Sazabi MCP to check open critical issues.
Use Sazabi MCP to query checkout error logs from the last 30 minutes.
Use Sazabi MCP to search Sazabi threads about payment latency.
Use Sazabi MCP to show recent automation failures.

Sazabi MCP lets Slackbot discover the available Sazabi actions and run the ones you're authorized to use. You can use it to investigate incidents, review logs, and take supported actions in the same Slack conversation.

Common workflows include:

Slackbot MCP access is scoped to the connected Slack workspace and the linked Sazabi user, and to the actions your Sazabi account is authorized to take. If Slackbot cannot access Sazabi for your request, make sure the workspace is connected and that your Slack email matches your Sazabi account email.