If your webhook receiver sits behind an API gateway or a proxy that checks tokens, mabl webhooks could not reach it. Every request went out with a fixed set of headers and no way to add your own. Now you can attach custom HTTP headers to any workspace webhook, so an Authorization token or a routing header travels with every request mabl sends.
Webhooks are editable now too. Changing a target URL or a trigger used to mean deleting the webhook and building a replacement from scratch. Open one from Settings > Webhooks and change what you need.
Creating and editing webhooks requires the editor role or above. A webhook can carry up to 20 headers. Header values are stored encrypted, and mabl rejects header names it sets on the request itself, such as Content-Type and User-Agent.
Try it out
- Go to Settings > Webhooks.
- Click on + New webhook, or click on an existing webhook to edit it.
- Under Custom HTTP headers, select Add header.
- Enter the header name and value.
- Save the webhook.
Every request mabl sends to that webhook now carries the headers you added.