Slack

Slack is where investigations happen, and it is the second place alerts arrive. It is one setup: a channel you connect once receives your alerts and, with one toggle, gets each of them investigated in the thread. Everything is under Settings > Integrations.

You do not need Slack to be notified. Alerts, new issues, and API test state changes go to your workspace’s email channel out of the box. What Slack adds is the investigation: an agent working the problem in the thread under the alert, which email cannot carry.

Not on Slack? Email info@fixter.dev with the channel you use and we will work on getting it connected.

Connect and add a channel

1. Connect your workspace. In Settings > Integrations, use the Slack Connect button and authorise Fixter. Once connected it shows your workspace name.

2. Add a channel. Give it a display name and the Slack channel id. Your first channel becomes the default, which is where notifications go when you have not routed them anywhere more specific.

3. Invite the bot in that channel, from Slack itself:

   /invite @Fixter

   Nothing arrives until the bot is invited

   The bot cannot read or post in a channel it has not been invited to, and this is the most common reason Slack “does not work”.

Turn on investigations

Each channel has an auto-investigate toggle. With it on, every alert posted to that channel is investigated automatically. While the agent works, a single progress line in the thread shows what it is doing (Investigating · Searching logs). It is deleted when the result is posted. There is no separate rule to configure; the toggle is the whole control. Optional per-channel exclusions let you skip specific alerts you never want investigated.

Whether or not auto-investigate is on, you can always start an investigation by hand: mention the bot on any thread and ask.

@Fixter what's going on with checkout here?

Where alerts get sent

Connecting a channel makes it available; it does not by itself decide what lands in it. Routing is set per source under Settings > Notifications: alerts, issue tracking, and API tests each point at the channels you choose, and a single alert rule or API test can be routed on its own. Anything unrouted goes to your email channel plus this default channel. See Alerts.

Issue digests

Fixter can also post a digest of the issues that need attention to one Slack channel, on the days and at the hour (UTC) you choose. Turn it on with the set_issue_digest_config MCP tool; it needs the channel it posts to.

If Slack is not behaving

• The bot never responds. It has not been invited to that channel. Run /invite @Fixter there.
• Alerts do not arrive at all. Check the channel is connected under Settings > Integrations, and that the alerting source points at it under Settings > Notifications.
• Alerts arrive but are not investigated. Auto-investigate is off for that channel, or an exclusion is matching. Turn the toggle on, or mention the bot to investigate by hand.

Still stuck? Email info@fixter.dev and one of our founders will help you fix your problem asap.

Related

• Investigations: what the bot does once it can see an alert
• Alerts: configuring what gets sent to Slack
• GitHub: the other connection investigations can use, for the fix flow