Slack
Slack is how a REVIEW can be answered outside the Vulnify app. The connection is configured in the app, under Integrations. It is not an SDK method.
The app offers two Slack modes. They are not interchangeable on one integration. To switch modes, add another integration.

Slack app
Section titled “Slack app”The Slack app puts Approve and Deny on a review alert. Install it with Add to Slack. That starts an OAuth install into your workspace. Only owners and admins can connect Slack. Until someone does, the card says Slack is not connected and that owners and admins can connect it here.
After the install, the page says: “Slack is connected. Pick the channel and alerts, then send a test.”
Choose channel lists public channels the app can see. Private channels are marked private. If the bot is not a member yet, the row says bot not in channel yet. The bot has to be in the channel before it can post. For a private channel, open it in Slack and run /invite @Vulnify. Then send the test again.
Approve and Deny in Slack can be on or off for that integration:
| Setting | What reviewers see |
|---|---|
| Yes, for review alerts | Approve and Deny buttons on the review alert. |
| No, alerts only | The alert is posted. Reviewers answer in the Vulnify app. |
Approving a HIGH or CRITICAL review still asks for an authenticator code when the reviewer has MFA on.
A request that did not come from Slack is rejected. If Slack buttons over HTTP are not enabled on the deployment, the app reports SLACK_INTERACTIONS_DISABLED and reviewers answer in the Vulnify app.
The app can also accept a bot token (xoxb-…) instead of OAuth, for a Slack app you created. Pasting a bot token can be turned off on a deployment. When it is off, the app says to use Add to Slack. The token is stored encrypted and is not shown again.
Disconnecting the Slack app revokes the bot token at Slack and stops new posts. Open messages can keep their buttons, and clicks on those buttons are refused. The integration history stays so you can reconnect.
Reinstall when scopes change
Section titled “Reinstall when scopes change”If the connection is missing the channel permissions, the channel list reports that a reinstall is needed and the page shows Reinstall Slack app. Install again, then choose a channel. The friendly message for that state is SLACK_REINSTALL_NEEDED.
Error codes
Section titled “Error codes”The app shows these messages instead of a raw code.
| Code | What it means |
|---|---|
SLACK_BOT_NOT_IN_CHANNEL |
The Vulnify bot is not in this channel. In Slack, open the channel and run /invite @Vulnify, then send the test again. The app fills in the bot’s Slack name. |
SLACK_REINSTALL_NEEDED |
This Slack connection is missing the channel permissions. Reinstall the Slack app, then choose a channel. |
SLACK_CHANNEL_UNKNOWN |
That channel is not available to the Slack app. Choose one from the list. |
SLACK_CHANNELS_UNAVAILABLE |
Slack could not list channels right now. Try again in a moment. |
SLACK_DISCONNECTED |
Slack is disconnected. Reconnect it before posting or choosing a channel. |
Incoming webhook
Section titled “Incoming webhook”An incoming webhook posts alerts into the channel the webhook was created for. The URL must be https://hooks.slack.com/services/…. The app rejects other URLs.
This mode does not approve reviews. There are no Approve or Deny buttons. The channel field is a label for your team. An incoming webhook always posts to the channel it was created for.
An organization has one Slack incoming webhook. Open it to change the URL, the label, or which alerts it sends. Disconnecting deletes the stored URL. The webhook remains in Slack until you remove it there.
What gets posted
Section titled “What gets posted”Slack is notified about decisions. It does not receive the contents of your records. With the hosted Slack app, reviewers see enough to approve or deny the action. An incoming webhook only posts the alert. The decision and the review note stay on the Vulnify event.

