Creating tickets in Linear or Jira? Trunk’s built-in automatic ticketing is the recommended approach — it produces richer ticket bodies (failure history, impact, common failure reasons, code owners), manages the full ticket lifecycle (create, reopen, close), and has full dashboard support with tickets linked back to their test cases. Use webhooks for custom workflows or platforms without a built-in integration.
For Merge Queue webhook events (
pull_request.* and pull_request_batch.*), see the Merge Queue webhooks reference.Supported Events
Trunk lets you create custom workflows with event-triggered webhooks. Flaky Tests events are named with atest_case prefix. You can find all the events that Trunk supports in the event catalog:
Webhook Events | trunk.io - Svix
Test collection events
Every event carries atest_collection object with the ID of the test collection the test belongs to and a link to it.
Event payloads
test_case.monitor_status_changed
Emitted when a monitor activates or resolves for a test case.
v2.test_case.status_changed
Emitted when a test case changes status (e.g., becomes flaky or is resolved), as triggered by a monitor.
v2.test_case.quarantining_setting_changed
Emitted when someone sets a manual quarantining override on a test case. Fires on every change, including one that re-applies the value already in force. It does not fire when Trunk auto-quarantines a test.
Delivery reliability. If the webhook delivery provider rate-limits a request, Trunk automatically retries with exponential backoff, so a transient spike rarely drops an event. This applies to every Flaky Tests webhook event and needs no configuration on your side.
You can also find guides for specific examples here: