Sync project channels and threads from your Slack workspace
Slack brings your project channels into Brink — messages and thread replies, with authors resolved, and RFI/submittal mentions cross-linked to Procore.Who can connect: organization owners and admins. Connecting installs the Brink app into your Slack workspace.
On the Integrations page (Organisation view), click the Slack card, then Connect Slack in the drawer.
The Slack drawer before the first account is connected
2
Install to your workspace
You’ll be redirected to Slack to approve the installation. Brink requests channel history and member-name access for public channels, plus permission to post — which is only ever used by an agent action you approve.
3
Bind channels
On the Projects page, open the project’s Integrations tab and bind each project’s Slack channel. The picker lists public, non-archived channels only.
Add scope binding on a project's Integrations tab
Only public channels can be bound. Private channels and direct messages
are not available to Brink — if a channel is missing from the picker, check
whether it’s private or archived.
Channel messages and thread replies, with author names resolved
Late replies to recent threads are picked up by re-checking the 25 most recent threads on each sync
Deleted messages are removed from Brink
RFI and submittal numbers in messages are cross-linked to Procore records
Slack limits how fast history can be read, so the first import of a large
channel can take a while — Brink reads a capped number of messages per sync
and continues on the next one. Recent messages appear first; history fills in
over subsequent syncs.
If a bound channel stays empty, check that the Brink app is a member of that channel — Slack only returns history for channels the app has been added to. Invite it from the channel with /invite @Brink.
Slack access doesn’t expire, so this connection rarely needs reconnecting.
Disconnecting revokes the Brink app’s access in Slack and deletes the stored credentials.
