● Support

Slack ↔ Chatter Bridge

Last updated: May 11, 2026

This page is referenced by the Bind Slack ch editor in Chatter. For the full setup walkthrough, see the Slack Integration guide. This page covers the specific step of binding a Slack channel ID to a Chatter channel.

What does binding do?

Bridging connects one Slack channel to one Chatter channel by channel ID. Once bridged:

  • Messages posted in the Slack channel appear in the bound Chatter channel.
  • Messages posted in Chatter (with the Slack ON toggle enabled) forward to the bound Slack channel via the webhook URL set in Settings → Integrations → Slack.

The Slack channel ID and the webhook are independent settings — you bind the channel ID to receive Slack messages in Chatter, and you paste the webhook URL to send Chatter messages to Slack. Most users want both.

How to find your Slack channel ID

  1. In Slack, click the channel name at the top of the channel.
  2. Click About.
  3. Scroll to the bottom of the panel.
  4. The Channel ID is shown — copy it. Looks like C0123ABC (public), G0123ABC (private), or D0123ABC (DM).

How to bind in Chatter

  1. Open Chatter in GovMatrixIQ.
  2. Pick the Chatter channel you want Slack messages to land in (e.g. #general).
  3. In the channel header, click the Bind Slack ch pill.
  4. A small editor opens. Paste the Slack channel ID.
  5. Press Enter or click outside the input to save.
  6. The pill changes to show → C0123ABC (the bound ID).

To unbind: click the pill again, then click Unbind.

Prerequisites the bridge needs to fire

Each of these must be true before Slack → Chatter messages flow:

  1. The bot is installed in your Slack workspace. Verify by opening a Slack DM with @GovMatrixIQ.
  2. The bot is a member of the source Slack channel. Run /invite @GovMatrixIQ in the target channel.
  3. Your Slack user is connected to a platform account. Run /govmatrix connect in any channel the bot is in, then click the Connect Account button.
  4. The Slack channel ID is bound to a Chatter channel — this page's instructions.
  5. The Slack workspace has the bot's Event Subscriptions enabled. Platform admins configure this once per workspace; your IT contact should know.

If any of these is missing, your Slack messages won't appear in Chatter. The bot drops un-routable messages silently.

Common bind errors

ErrorMeaningFix
"slack_channel_id must be a valid Slack channel ID" Pasted value doesn't match expected format (C/G/D + 6-24 alphanumeric chars) Double-check you copied the Channel ID (e.g. C0123ABC), not the channel name (e.g. general)
Save appears successful but no messages arrive Bot not in the bound channel Run /invite @GovMatrixIQ in the Slack channel
Save appears successful but only YOUR Slack messages arrive Other team members haven't connected Each user must run /govmatrix connect once
Messages appear but author shows "Slack User" instead of name Sender's Slack user isn't connected to a platform account Sender runs /govmatrix connect; subsequent messages show their platform name + role

Privacy

  • The bot subscribes to every channel message in channels it has been invited to. Posts from unconnected users are dropped, but the bot still receives the event payload.
  • Inbound messages are stored as plaintext in Chatter (encryption is off for inbound). Slack itself stores messages unencrypted, so this does not increase exposure.
  • Outbound forwarded messages travel through the platform server briefly (in-flight, HTTPS) before going to Slack. The platform never persists the plaintext of an encrypted Chatter message.

Need help?

Open a support ticket with your organization name, the Slack channel ID you tried to bind, and the Chatter channel name.