Get Tagged in CircleCI Slack Build Notifications
You can link your CircleCI identity to your Slack identity so CircleCI will @-mention you directly in Slack notifications for workflows you triggered. This makes it easy to spot your own builds in a shared channel without scanning through commit SHAs or pipeline URLs.
Note: This feature requires the native CircleCI Slack integration. It is not supported for notifications sent through the legacy Slack orb.
Before you start
Confirm the following are already in place:
Your organization has the CircleCI Slack app installed — check under Org Settings > Slack Integration
Your project is connected to a Slack channel — check under Project Settings > Slack Notifications
If either of these isn't set up yet, see Slack integration in the CircleCI docs.
Link your Slack identity
Go to your CircleCI user settings.
Find the Slack section and select the option to link your identity.
Authorize the connection in Slack when prompted.
Once linked, CircleCI will @-mention your Slack handle in workflow notifications for any pipeline you trigger.
Troubleshooting
I linked my account but I'm not being tagged.
Confirm your project has a Slack channel configured under Project Settings > Slack Notifications.
Make sure you're using the native CircleCI Slack integration, not the Slack orb — orb-based notifications don't support tagging.
Check that the Slack workspace connected to your CircleCI org is the same workspace where you linked your identity.
The Slack section doesn't appear in my user settings.
Your org may not have the CircleCI Slack app installed yet. An org admin will need to install it from Org Settings > Slack Integration first.
I'm getting tagged in the wrong Slack workspace.
Each CircleCI org can only connect to one Slack workspace. If you belong to multiple orgs with different workspaces, tagging will only work in the workspace tied to the org that owns the triggering pipeline.