Slack
Slack bridge availability and the distinction from incoming alerts.
- Which platform
- Slack. Conversation bridge setup is unavailable.
- What relays in each direction
- No supported customer bridge relays messages in either direction.
- What does not relay
- No supported bridge exists for messages, threads, files, reactions or surfaces.
- Where the record stays
- Existing Slack messages stay in Slack. Application messages remain in their own conversation.
- The origin badge
- There is no supported Slack bridge flow with an origin badge guarantee.
- What happens when the bridge is removed
- There is no customer bridge removal control.
Planned Slack bridge setup is unavailable in the application. Integrations has no Slack install, bind or disconnect control.
Message relay
A Slack conversation bridge would link a Slack conversation to a channel. This is different from a provider behind a surface and from an incoming webhook that posts an alert. An alert arriving in a channel doesn’t establish a two-way Slack bridge.
Current limits
There is no supported procedure for choosing a Slack workspace, granting scopes or binding a Slack channel. Neither relay direction is available through a customer setup flow. Thread correspondence, sender attribution, origin badges and prevention of repeated relay are not supported bridge guarantees today. Threads, files, reactions, edits and deletions have no supported synchronisation.
Slack conversation remains accessible directly in Slack. The application doesn’t offer Slack reconnect or bridge removal controls. The provider reference lists available connections.