Custom alert webhooks

The Custom messaging service sends an HTTP POST with a JSON body to an endpoint you control. Use it to connect Bugsink to an internal notification service or another system without a built-in integration.

Configure the endpoint

1. Open Projects and select the project’s megaphone icon (Alerting Settings).
2. Select Add, enter a display name, and choose Custom.
3. Enter the endpoint’s webhook URL and save.
4. Select Test and confirm that your endpoint returns a successful HTTP status.

Bugsink sends Content-Type: application/json. The payload contains the fields from Bugsink’s canonical issue API, plus these convenience fields:

• title: the displayed issue title.
• project_name: the Bugsink project name.
• url: the absolute URL of the issue in Bugsink.
• alert_reason: NEW, REGRESSED, UNMUTED, or TEST for a test message.
• unmute_reason: present when an issue was unmuted by a condition.

The test message uses representative issue data rather than an existing issue. The Bugsink API documentation describes the canonical issue fields.

Responses and failures

Return a response below 400 to mark delivery as successful. Bugsink stores the most recent connection error, HTTP status, and up to 2,000 characters of the response body when delivery fails. A later successful delivery clears that failure.

Webhook URLs are subject to Bugsink’s Webhook Outbound Policy. Self-hosted installations can use that policy to allow specific internal destinations when required.

See the alerts overview for alert conditions and multiple destinations.