Slack integration

The Slack integration sends important Errorgap activity to the channels your team already uses. Connect it at the project level so errors, regressions, and incident updates reach the people who own the application.

What Slack is for

Slack is best for timely awareness and lightweight coordination. Use it to notify teams when new failures need review, when a resolved error regresses, or when an incident needs attention.

• Send new production error groups to an owning team channel.
• Notify responders when a resolved group regresses.
• Share incident status changes where teammates can see them.
• Link back to Errorgap so investigation continues with full context.

Before you connect

Decide which Slack channel should receive notifications for the project. The best channel is usually the one monitored by the team that owns the application or service.

• Confirm the project boundary and owning team are clear.
• Choose a channel where alerts will be noticed and acted on.
• Avoid broad channels unless multiple teams truly share ownership.
• Make sure teammates know Errorgap links are the source of detail.

Connect a project

1. Open the project you want to connect.
2. Go to project settings and open integrations.
3. Select Slack.
4. Choose or confirm the Slack workspace and destination channel.
5. Save the integration settings.
6. Send or wait for a test notification to confirm the channel receives messages.

If your organization has already authorized Slack, connecting a project should only require choosing the project-level destination and notification behavior available to you.

Choose alert destinations

Route notifications to the smallest useful audience. A channel with clear ownership is more effective than a broad channel where alerts become background noise.

• Use service-specific channels for service-specific projects.
• Use incident or on-call channels for high-severity operational updates.
• Use quieter project channels for low-severity or non-production notifications.
• Review channel ownership when teams or project boundaries change.

Tune notifications

Tune Slack notifications so they prompt action without flooding the channel. Start with the highest-signal events, then broaden only if the team needs more visibility.

• Notify on new unresolved production groups.
• Notify on regressions after a group was resolved.
• Notify on incident creation or important incident status changes.
• Reduce non-production or low-priority noise unless the channel is intended for it.

Use Slack during response

Slack is useful for coordination, but Errorgap should remain the place where investigation context lives. Use Slack messages to pull people into the work, then keep state, ownership, and links current in Errorgap.

• Open the Errorgap link before asking teammates to diagnose from a message preview.
• Assign the error group or incident once someone owns the next step.
• Link any external issue or incident discussion back to the Errorgap record.
• Resolve, mute, or update state after the response changes.

Troubleshooting

If Slack messages are missing or going to the wrong place, start with the project-level integration settings and channel choice.

• Confirm the Slack integration is enabled for the project you are viewing.
• Check that the selected channel is the expected destination.
• Confirm the event type you expected is enabled for notification.
• Check whether environment or severity filters exclude the event.
• Send a test notification or trigger a safe test error to confirm delivery.