Slack Alarm Channel (OAuth)

What the channel does

A Slack alarm channel is a delivery destination. Connecting it does not create a detection rule or make every Cremit event appear in Slack. Select the channel in an enabled alarm rule or a workflow notification action. The event must match that configuration before Cremit attempts delivery.

The message carries the configured alert text and, when available, a link to the relevant Cremit detail or action request. Investigate, assign and close work in Cremit. The current Slack message does not provide in-message acknowledge, assign or dismiss controls or automatic status threads. Delivery can be delayed or fail, so a Slack post is not proof that every source was scanned.

Connect and choose a channel

In Cremit Platform, open Configuration → Alarms → Channels and add a Slack app channel. Complete Slack authorization, then choose the destination channel in Cremit. For a public channel, Cremit attempts to join the app. For a private channel, make sure the app is a member and can post. Workspace policy may limit who can authorize an app.

Slack scan sources and Slack alarm channels serve different purposes. Connecting this alarm channel does not grant scan coverage of its messages. If you use a Slack incoming webhook instead, configure it as a webhook delivery channel; it is a separate route from this OAuth channel.

Choose when to send

Create or edit an alarm rule under Configuration → Alarms and select the connected channel. Rule triggers include supported active-secret, public active-secret, incident and scan-source verification events. A workflow can also send a notification to the channel when its trigger, conditions and stage run. Check each rule or workflow rather than assuming one connection enables every event.

Verify delivery and investigate gaps

Check that the channel is connected and enabled. Use the channel test action to send a harmless sample message to the chosen Slack destination. Then inspect the enabled rule or workflow and the alarm log or workflow run after a matching event. A preview shows formatting; it does not prove delivery. Never expose a working key just to test an alert.

If no message arrives, confirm channel membership and posting permission, channel connection status, the rule or workflow destination and its conditions, and the delivery record. A source scan must also finish and produce a matching event before a detection alert can be sent. Fix a failed connection or permission before retrying.

Primary documentation

Slack chat.postMessage and channel membership

Slack chat:write scope

Cremit scanning scope