Skip to main content

​
Slack Integration

Corridor integrates with Slack to post PR review findings to a channel you choose and answer questions about your projects when you mention it in a public channel.

​
What you get

  • PR review notifications: When Corridor finds vulnerabilities in a pull request, a summary is posted to a channel you choose
  • The Corridor bot: Mention @Corridor in a channel to ask questions about your code and security findings
  • Threaded conversations: Follow-up questions continue in the same Slack thread with full context
  • Dashboard visibility: Conversations started in Slack also appear in the Corridor dashboard alongside your other chats

​
Connecting Slack

You need to be a Corridor team admin to set up the Slack integration. You’ll also need permission to install apps in your Slack workspace. If Slack blocks the install, see Troubleshooting.
1

Open your team settings

In the Corridor dashboard, go to your Team page and find the Integrations section.
2

Add the integration

Click Add Integration and select Slack, then click Connect with Slack.
3

Authorize Corridor

A Slack window opens asking you to authorize Corridor for your workspace. Review the permissions and click Allow.
4

Choose a notification channel

Once connected, the Configure Slack Integration dialog opens. Pick the public channel where PR review notifications should be sent. The Corridor bot joins the channel automatically.
5

Set a default project

Choose a Default Project for the chatbot. When someone messages @Corridor in Slack, conversations use this project for context. Click Save.
Notifications start with the next pull request review that finds vulnerabilities.

​
Changing your settings

To change the notification channel or default project later, go back to the Integrations section on your Team page and click the channel name on the Slack integration. Each Corridor team connects to one Slack workspace.

​
PR review notifications

Whenever Corridor reviews a pull request and finds vulnerabilities, it posts a message to your notification channel with:
  • The number of vulnerabilities found, with a link to the pull request
  • A short summary of each finding, so you can gauge severity at a glance
Messages are only posted when a review finds vulnerabilities. Clean reviews don’t post anything.

​
Chatting with @Corridor

Mention @Corridor in any public channel the bot has joined, followed by your question:
Corridor replies in a thread under your message. To ask a follow-up, mention @Corridor again in the same thread. It keeps the conversation context, so follow-ups build on earlier answers.

​
What you can ask

The bot answers questions using your default project’s context. For example:
  • “What open findings do we have right now?”
  • “Explain this SQL injection finding and how to fix it”
  • “Which repos had the most findings this month?”
  • “What does this guardrail check for?”
Anyone on your team can chat with the bot, and several people can join the same thread. Corridor responds to each mention in context.
Conversations started in Slack also appear in the Corridor dashboard, in Corridor Agent and on your project’s Chats page, marked with a Slack icon, so you can pick them up later or share them with teammates.

​
Good to know

  • The bot works in public channels only. It doesn’t respond to direct messages or private channels
  • Corridor only processes messages that mention @Corridor, including thread replies
  • You need a Corridor account to use the bot. Corridor matches your Slack profile to your Corridor account by email. If they don’t match, ask your team admin to invite you at the email address you use for Slack

​
Troubleshooting

​
”Apologies, but Corridor can’t be installed”

This message comes from Slack, not Corridor. Corridor isn’t listed in the Slack Marketplace, so Slack only lets a workspace owner install it. On Slack Enterprise Grid, this may need an org owner. To get it installed:
  1. Find out who owns your Slack workspace. In Slack, go to Settings & administration > Manage members and filter by “Owner”
  2. When the owner is ready, go to Team > Integrations in Corridor and click Connect with Slack. A Slack authorization page opens in a popup. Copy the link from the popup’s address bar
  3. Send that link to the workspace owner right away. The link works once and expires after about 10 minutes. The owner opens it, signs into your Slack workspace, and clicks Allow
Once they approve, the Corridor app shows up in your Slack workspace and you can invite it to any channel with /invite @Corridor. If your company uses Slack’s app approval process, click Request to install on the error screen instead. Once a Slack admin approves the request, click Connect with Slack again to get a fresh link and open it yourself to finish the install. The old link won’t work anymore.

​
Notifications aren’t arriving

  1. Confirm a notification channel is set: on your Team page, the Slack integration should show a channel name rather than Configure Channel
  2. Notifications are only sent when a review finds vulnerabilities. Clean reviews don’t post anything
  3. If the channel was archived or renamed, reselect it in the integration settings

​
The bot isn’t responding

  1. Make sure you mentioned @Corridor. The bot only processes messages that mention it
  2. Check that you’re in a public channel, not a DM or private channel
  3. If the bot says you need a Corridor account, ask your team admin to invite you using the same email address as your Slack profile
Still stuck? Contact support@corridor.dev.