Send Logfire Alerts to Slack with the Slack App
The Logfire Slack app brings your observability notifications into Slack. Install it into your workspace once, connect it to your Logfire organization, and then send any alert or issue to a channel by picking that channel from a list.
- Posts notifications to the channels you choose: a firing alert or a new issue, rendered as a Slack message with a link back to Logfire.
- Lists the channels it has been invited to, so you pick a destination instead of pasting a URL.
- Publishes a Home tab describing the connection.
- Reads 👍 / 👎 reactions on the messages it posted. This is how you rate a finding from Logfire’s site reliability engineering (SRE) agent, which is enabled for selected organizations rather than generally available. Reacting to an alert or issue notification does nothing.
The app never posts anywhere it has not been invited, and it does not join channels by itself.
| Permission | Why the app needs it |
|---|---|
chat:write | Post notifications into the channels you pick |
channels:read, groups:read | List public and private channels the app is a member of, for the channel picker |
reactions:read | Receive the đź‘Ť / đź‘Ž you add to an SRE agent finding, as your rating of it |
reactions:write | Acknowledge that rating with a reaction of its own |
team:read | Show the workspace name and icon on the connection in Logfire |
The app does not read your message history or your direct messages.
Logfire stores the workspace grant (the bot token, encrypted at rest), the workspace’s name and ID, the granted permissions, and the ID of each channel you select. Message content flows one way: Logfire posts notification text built from your telemetry, and the only inbound content it records is the reaction feedback described above.
See the Pydantic privacy policy for how we collect, manage, and store this data.
You need:
- In Logfire: permission to change organization settings. The Connections page is visible to members who can write to the organization, typically an owner or admin.
- In Slack: the ability to install an app into your workspace. Many workspaces restrict this to admins, or route it through an approval request.
- A channel to post into, and the ability to invite an app to it.
Connections are organization-level: one workspace install serves every project in the organization.
- Open your organization’s Settings, then Connections under Developer.
- Find the Slack row and click Connect.
- Slack asks which workspace to install into and lists the permissions the app requests. Approve it.
You land back on Connections, where the Slack row now names the connected workspace.
In Slack, run this in the channel you want notifications in:
/invite @Logfire
Logfire only lists channels the app is a member of, so this step is what makes a channel selectable. It also means a channel you can pick is a channel Logfire can post to.
A notification channel in Logfire is a destination you attach to alerts and issues.
- In your project, go to Delivery → Channels in the Notify section of the sidebar, then click New channel. You can also create one inline from the Send notifications to section of an alert form.
- Name it. This is a Logfire label, not the Slack channel name.
- Pick Slack App as the type. (Slack Webhook is the other route, covered in Setup Slack Alerts.)
- Pick the Slack workspace you connected.
- Pick the Slack channel. Only channels the app was invited to appear here.
- Click Send test message. A sample notification posts to the channel.
The test must succeed before the channel can be created. That is deliberate: a Slack destination that silently drops messages is worse than no destination, and the moment to find out is now rather than during an incident.
Select the channel anywhere Logfire sends notifications:
- Alerts: the Send notifications to section of the alert form. See the alerts guide.
- Issue notifications: the notification settings on the Issues page, or the filter alert on a saved search. Both send the same issue notification, so pick whichever fits how you already scope issues.
One channel can serve many alerts, and one alert can notify several channels.
The channel I want is not in the list. The app is not in it. Run /invite @Logfire in Slack, then reopen the list.
Private channels are missing. Workspaces connected before Logfire asked for private-channel access can only list public channels, and the channel picker says so. Reconnect Slack under Settings → Connections to include them.
The workspace has more channels than the list shows. Very large workspaces are listed up to a limit, and the picker’s search covers only what it listed. Invite the app to the channel you want, then look again.
Notifications stopped arriving. Check the alert’s run history: a failed delivery is recorded against the channel. The usual causes are the app being removed from the channel, the channel being archived, and the app being uninstalled from the workspace. Reopen the channel and use Send test message to confirm a fix.
A test message fails with an invite instruction. The app was removed from the channel after you selected it. Re-invite it and test again.
- Disconnect in Logfire (Settings → Connections) to revoke the grant. Channels using that workspace stop delivering.
- Uninstall in Slack to do the same from the other side. Logfire marks the install revoked and its channels stop working until you connect again.
A Slack install belongs to the workspace, so if several Logfire organizations connected the same workspace, revoking affects all of them. Reconnecting is a fresh install rather than a repair: the old grant is gone.
Some workspaces will not approve a third-party app, or route the request through an approval you would rather not wait for, while still letting members build an app of their own. In that case Logfire also delivers through an incoming webhook, which you create in your own Slack app and paste into a notification channel: see Setup Slack Alerts. If your workspace allows neither, ask an admin to approve the Logfire app; there is no third route.
That route works, but it puts a bearer secret in your hands, fixes each webhook to a single channel, and gives Logfire no way to tell you whether the destination is still reachable. Prefer the app when you can install it.