Skip to main content
Send alerts to Corelayer for investigation. Each webhook has its own URL and authentication settings.

​
Add a webhook

Open Webhooks from the sidebar and click Add Webhook. Choose a Webhook type:
  • incident.io: Send alerts and declared incidents using an incident.io signing secret.
  • Honeycomb: Send trigger alerts using a webhook recipient and shared secret.
  • CloudWatch: Forward alarm state changes through an EventBridge API destination.
  • Datadog: Send monitor notifications using a webhook payload template.
  • Custom alerts: Send alerts in Corelayer’s JSON format using a bearer token.
Enter a Source name, such as Production incidents, so you can recognize the webhook in the list.

​
Manage sources

Open Webhooks and expand a source to view its URL and authentication details.

​
Enable or disable

Use the source’s Enabled switch. The change takes effect as soon as it succeeds. Disabling keeps the webhook’s configuration. Incoming requests receive 403 until you enable it again.

​
Delete a source

Select the checkbox beside each source you want to delete, then click Delete selected. Review the source names in the confirmation and choose Delete webhook or Delete webhooks. Choose Cancel to keep them. Also remove the webhook from the system sending alerts so it stops calling the deleted URL.

​
Rotate a token

For a webhook that uses a bearer token, expand the source and click Rotate token beside its masked token. Confirm the rotation, then copy the new token from the completion dialog before closing it. The new token is shown once. Update your alert sender with the new token. The old token stops working immediately after rotation. incident.io webhooks use a signing secret from incident.io instead of a Corelayer bearer token. Need help? Contact support.