Webhook
Send FixSense analysis events to any external system via webhook.
Overview
FixSense can send real-time events to any URL — connect to Zapier, n8n, Make, Jira, Linear, or your own custom endpoint. Every time a test failure is analyzed or an auto-fix runs, FixSense sends a JSON payload to your webhook.
Events
| Event | Trigger |
|---|---|
| analysis.completed | A test failure analysis finishes |
| autofix.triggered | Auto-fix agent starts working on a failure |
| fix.merged | An auto-fix PR is merged |
| fix.verified | CI passes after the fix is merged |
Setup
- Open your FixSense Dashboard
- Scroll to the Integrations section
- Paste your endpoint URL into the Webhook input field
- Click Save
FixSense will generate a signing secret — save it immediately, as it's only shown once. Use this secret to verify that incoming requests genuinely come from FixSense.
Payload Format
Every webhook request is a POST with a JSON body:
{
"event": "analysis.completed",
"timestamp": "2026-03-13T10:30:00.000Z",
"data": {
"repo": "your-org/your-repo",
"testName": "login.spec.ts > should redirect after login",
"rootCause": "Selector changed from #submit to .btn-primary",
"flakinessScore": 15,
"confidence": "high"
}
}Signature Verification
Each request includes these headers:
| Header | Description |
|---|---|
X-FixSense-Event | Event type (e.g. analysis.completed) |
X-FixSense-Signature | HMAC-SHA256 hash of the request body, signed with your webhook secret |
Content-Type | application/json |
To verify a request, compute the HMAC-SHA256 of the raw request body using your signing secret and compare it to the X-FixSense-Signature header.
Use Cases
- Create Jira or Linear tickets automatically when a real bug is detected
- Post to Slack or Teams with custom formatting via Zapier/n8n
- Feed a dashboard or monitoring tool with failure data
- Trigger custom CI workflows based on analysis results
Disconnect
To stop sending events:
- Go to the FixSense Dashboard
- In the Integrations section, click Disconnect on the Webhook card
FAQ
Does FixSense retry failed webhook deliveries? No. Webhook notifications are fire-and-forget. If your endpoint is down, the event is skipped. This ensures that webhook issues never block your CI analysis or auto-fix workflows.
Can I filter which events are sent?
Currently, all event types are sent to your webhook URL. You can filter events on your end by checking the event field in the payload.
Is HTTPS required? Both HTTPS and HTTP URLs are accepted, but HTTPS is strongly recommended for security.