Webhooks
Receive real-time event notifications from Featurely to your own endpoints.
Webhooks
Featurely can send HTTP POST requests to your own endpoints whenever events occur in your project. Configure webhooks in your dashboard under Settings → Webhooks.
Supported events
| Event | Triggered when |
|---|---|
monitoring.down | A monitored site goes down |
monitoring.recovered | A monitored site comes back up |
error.new | A new error is captured |
error.resolved | An error is marked as resolved |
feature.created | A new feature request is submitted |
feature.status_changed | A feature request's status changes |
bug.created | A new bug report is submitted |
bug.status_changed | A bug report's status changes |
Payload format
All webhook deliveries send a POST request with Content-Type: application/json and a body in the following shape:
{
"event": "error.new",
"projectId": "your-project-id",
"timestamp": "2024-01-15T10:00:00.000Z",
"data": { }
}The data object contains the resource that triggered the event. Its shape varies by event type.
Platform integrations
Featurely auto-detects the webhook destination and formats the payload accordingly:
| URL pattern | Format |
|---|---|
discord.com/api/webhooks/… | Discord embed |
hooks.slack.com/… | Slack incoming webhook |
webhook.office.com/… / logic.azure.com/… | Microsoft Teams adaptive card |
| Anything else | Generic JSON (payload shown above) |
Testing a webhook
Use the Test button in Settings → Webhooks to send a test payload to your endpoint. The response status, latency, and any error messages are shown in the dashboard.
Retry behaviour
If your endpoint returns a non-2xx status code or times out, Featurely does not automatically retry — deliveries are fire-and-forget. Use the test button to verify your endpoint is reachable.
Security
Webhooks are sent over HTTPS. To verify that a delivery originated from Featurely, check that the request comes from Featurely's servers and validate any fields you rely on (e.g. projectId matches your own project).