Using a webhook as an alert hook is a great way to manipulate the notification data any way your team prefers.
Tips for setting up a webhook
- The webhook must reply with a 200 response code. If you need to do extra work that needs error handling, do it outside of the request handler.
- The webhook must respond within 5 seconds.
- If a code is returned that is not 200, the webhook will be retried up to 4 times serially. If a valid response is not returned, you may not receive the event data again.
- The webhook is called as an HTTP POST with the event data as JSON.
- HTTP or HTTPS protocols are supported, but HTTPS endpoints must have proper certificates installed.
- You may need to exempt the webhook route from CSRF protection.
- Need to verify the event payload? Just check the project token inside the data to ensure it matches your records.
If you find any out of date info, errors, or just have any other questions, you can hit up our engineers and our community of users directly on Slack.