Firetiger App for Slack
Firetiger is an AI agent platform for production monitoring. Firetiger agents identify and fix problems in production by combining observability data, codebase understanding, and knowledge of your business.
The Firetiger app for Slack connects your Slack workspace to Firetiger so that agents can send real-time notifications and alerts directly to your Slack channels. When an agent detects an issue, investigates a root cause, or deploys a fix, it can post updates to the channels you configure — keeping your team informed without leaving Slack.
AI Disclaimer: Firetiger uses AI agents to analyze observability data and generate insights. AI-generated content, including messages sent to Slack, may occasionally contain inaccurate or incomplete information. Users should verify critical findings independently.
Installation
- Navigate to Integrations in the Firetiger UI
- Click New Connection
- Select Slack as the connection type
- Click Install App for Slack
- In the popup, select your Slack workspace and click Allow
The connection will be created automatically with your workspace details.
What Gets Created
When you install the Firetiger app for Slack, Firetiger automatically creates a connection with:
| Field | Value |
|---|---|
connection_id |
slack-{workspace_id} (e.g., slack-t1234567890) |
display_name |
Your Slack workspace name |
description |
Slack workspace: {workspace_name} |
Agent-Specific @mentions
After Slack is connected, you can reserve custom Slack handles for individual agents, such as @checkout-oncall. Create a Slack @mention trigger on the agent’s Plan page, then create or select a SlackHandle and choose the channels where that agent should respond.
Custom handles are Slack user groups, so this feature requires a Slack workspace with user groups — typically Business+ or Enterprise Grid. If an admin restricts user-group creation, ask them to create the Slack user group first, then add that existing handle in Firetiger. See Create a Custom Slack Handle for an Agent → Slack workspace requirements.
See Create a Custom Slack Handle for an Agent for the full setup flow.
Permissions
The Firetiger app for Slack requests permissions for messaging, channel access, reactions, custom handles, and user lookup. Key permissions include:
| Scope | Purpose |
|---|---|
channels:read |
List available channels |
channels:join |
Join public channels to send messages |
chat:write |
Send messages to channels |
chat:write.public |
Send messages to public channels without joining |
team:read |
Get workspace information |
usergroups:read |
Find Slack user groups used for custom agent handles |
usergroups:write |
Create Slack user groups for new custom agent handles |
users:read |
List users for mentions |
Re-authorization
To update permissions or reconnect a workspace:
- Navigate to Integrations
- Find your Slack connection
- Click Reconnect or delete and recreate the connection
Slack scopes are additive - re-authorizing adds new permissions without removing existing ones.
Tools
Slack connections enable the following agent tools:
| Tool | Description |
|---|---|
slack-send-message |
Send messages to one or more Slack channels |
slack-send-message
Send notifications to Slack channels. Supports Slack’s mrkdwn format for rich text.
Parameters:
| Parameter | Required | Description |
|---|---|---|
connection |
Yes | The Slack connection to use |
channels |
Yes | List of channel names or IDs (e.g., ["#alerts", "C1234567890"]) |
message |
Yes | Message content (use Slack mrkdwn: *bold*, _italic_, `code`) |
title |
No | Optional title displayed as a bold header |
investigation_url |
No | Optional URL to link back to an investigation |
Description Field
The description field helps agents understand when to use this Slack workspace.
Example:
Primary workspace for engineering alerts.
Use for:
- Incident notifications → #incidents
- Deployment updates → #deployments
- Agent status updates → #firetiger-alerts
Best Practices
- Use descriptive workspace names - Helps agents select the right workspace when multiple are connected
- Document channel conventions - Include which channels to use for different alert types
- Limit to necessary workspaces - Only connect workspaces that agents need to notify