BugSmash + Webhooks

Send BugSmash feedback events to your endpoint

Q: What data does the webhook send?

The advanced guide provides event-specific example payloads with identifiers and relevant feedback context. Use the current example for each event as the implementation reference.

Q: How should I protect the webhook endpoint?

Protect the endpoint with your organization's normal authentication controls. For request verification, use the webhook secret key, X-Webhook-Timestamp, and raw request body to validate X-BugSmash-Signature as documented by BugSmash.

Q: Where do I choose the webhook events?

Choose the trigger events while adding the webhook under Workspace Settings → Integrations → Webhooks.

Use advanced webhooks to send real-time event data from supported BugSmash comment activity to an endpoint you control. Build custom notifications, issue-routing, reporting, or internal automation around the received payload.

Start with BugSmash View advanced webhooks guide

Protect the endpoint with appropriate authentication, then verify each X-BugSmash-Signature using the webhook secret key, X-Webhook-Timestamp, and raw request body.

Key Advantages

Build directly on BugSmash event data

Receive documented feedback events

Handle new comments, comment updates, replies, and status changes at your endpoint.

Control the destination workflow

Process the webhook payload in your own service, automation layer, or internal system.

Keep security in the design

Protect the endpoint with appropriate authentication and validate each webhook signature using the documented signing inputs.

Workflow Steps

From a BugSmash event to your custom workflow

Prepare the endpoint.

Protect the endpoint with appropriate authentication and preserve the raw request body for signature verification.

Configure the webhook.

Add the endpoint URL in BugSmash and choose the trigger events you want to receive.

Receive an event.

BugSmash sends payload data for a supported comment event.

Validate and process it.

Verify X-BugSmash-Signature with the webhook secret key, X-Webhook-Timestamp, and raw request body before using the event data.

Data Mapping

Webhook events documented by BugSmash

Event identifier	What changed
`new_comment`	A new comment was created
`comment_updated`	An existing comment was updated
`new_reply_on_comment`	A new reply was added to a comment
`status_changed`	A comment status changed

The official guide includes example payloads for these events. Depending on the event, the examples show identifiers and feedback context such as comment data, project or review references, status information, user information, and timestamps. Implement against the current documented payload for the event your endpoint receives.

Workflow in Action

Route a new comment through a custom service

Live Scenario BugSmash + Webhooks

Example workflow A team receives a `new_comment` event at its protected endpoint, verifies X-BugSmash-Signature from the webhook secret key, X-Webhook-Timestamp, and raw request body, then applies its own routing rules before creating a notification or delivery record.

Applications