Support Multiple Slack Channels Per Project for Notifications (New Slack Integration)
H
Henna Abbas
As part of the new CircleCI Slack integration, users need the ability to route different types of notifications from the same project to different Slack channels — for example, sending build notifications to one channel and chunk notifications to another.
Problem Statement:
The new Slack integration currently supports a single Slack channel per project for notifications. This creates friction in two distinct scenarios:
Notification type separation — Teams want different notification categories (builds, chunks, etc.) to go to different channels for better signal-to-noise management.
Cross-team pipeline ownership — When Team A owns a pipeline definition but Team B's work triggers failures in it, Team B currently has no way to route those failure notifications to their own channel. The only workaround is to make the pipeline never fail and post to Slack manually — which completely defeats the purpose of automated notifications.
Proposed Solution:
Within the new Slack integration, allow users to configure multiple Slack channel destinations per project, with the ability to filter/route by notification type (build, chunk, failure, success, etc.) and/or by pipeline definition.
User Stories:
- As a platform engineer, I want build notifications and chunk notifications to go to separate channels so each team stays focused on relevant alerts.
- As a downstream team, I want pipeline failure notifications routed to my channel even when I don't own the pipeline definition, so I can act on failures that affect my work without relying on the pipeline-owning team.