Webhooks
Last updated
Last updated
Trunk provides webhooks for you to build custom integrations to automate workflows, like notifying your team when a test becomes flaky or automatically creating tickets to investigate flaky tests. Trunk already provides a Jira integration, and more are planned. Webhooks lets you build custom integrations for use cases that are not supported out of the box.
Svix powers webhooks for Trunk. You'll be using Svix to configure webhooks and you should familiarize yourself with the Svix App Portal docs to learn more.
Trunk lets you create custom workflows with event-triggered webhooks. Flaky Test events are named with a test_case prefix. You can find all the events that Trunk supports in the event catalog:
You can also find guides for specific examples here:
Want to chat with Trunk's engineers? Join us and 1500+ fellow engineers on Slack.
You can configure webhooks, view the supported events, and see past webhook requests in the Trunk Web App under Settings > Organization > Webhooks.
If you're building custom apps to receive webhooks sent from Trunk, you should verify Webhooks to prevent malicious attacks from impersonation.
Svix provides a library in order to allow easy verification of these webhook signatures. Docs on how to set this up can be found here. If you wish to verify webhooks manually instead, you can find Svix docs on how to do that here.
From the "Logs" and "Activity" tabs, it's possible to view all emitted webhooks and their payloads and search them, examine the responses returned to us after processing a webhook and which ones failed, and resend webhook events. This allows you to have full insight into how your system is handling webhooks from Trunk.
