Webhook Alarm Channel
Send selected Cremit alarms to a public webhook endpoint with POST or GET and an optional receiver credential.
Key Features
- POST JSON or GET to a configured public URL
- No auth, bearer token, API key header or Basic auth
- Test delivery and alarm delivery history
- Routing through enabled alarm rules or workflows
Requirements
- 1A reachable public HTTP or HTTPS receiver; use HTTPS for credentials and alert data
- 2Permission to configure Cremit alarm channels and rules or workflows
- 3Any receiver credential required by your endpoint
Step-by-step setup guide
Review the steps needed to configure this integration.
What is sent
A webhook channel is a delivery destination. An enabled alarm rule or workflow must select it before matching events are sent. For POST, Cremit sends JSON with message, timestamp and metadata. Public metadata contains the trigger type, severity, event timestamp and delivery-target type when available. GET sends a request to the configured URL without that JSON body. Inspect a test request before building a receiver around a particular field.
The current channel has no HMAC signing option, X-Cremit-Signature header or built-in PagerDuty, Teams and Discord payload presets. A receiver that requires a different schema needs your own adapter. Use HTTPS and a receiver-side credential when the destination requires authentication. Do not treat a webhook request as cryptographically signed by Cremit.
Create and route the channel
In Cremit Platform, open Configuration → Alarms → Channels and add a Webhook channel. Enter a name and a publicly reachable URL. Choose POST for the JSON body or GET if the receiver expects a URL request. Choose no auth, bearer token, API key header or Basic auth to match the receiver. Localhost and private network addresses are rejected.
Save the channel, then select it in an enabled alarm rule or workflow notification action. Configure the rule or workflow conditions there. Creating the channel alone does not send every finding. A Slack incoming-webhook URL can also be used as a webhook destination; it follows a different connection path from the Slack OAuth channel.
Test and investigate delivery
After saving, use the channel test action with a harmless message. The request is queued, so a successful button response means the test was accepted for delivery, not that the receiver accepted it. Check the receiver and Cremit alarm log for the final result. Then inspect the rule or workflow and its delivery record after a matching event. Do not expose a live credential to generate a test.
If delivery fails, compare the receiver URL, method and authentication settings, then inspect its HTTP response and the Cremit delivery log. A receiver rejection can be a final failure; temporary errors may be retried. The current product does not provide the customer-facing five-attempt dead-letter replay or fixed delivery-time guarantee described in an older guide.
Get started now
Review the setup steps and required permissions for the Webhook integration.