Some applications need custom headers while talking to their API.
As an example NextCloud needs “OCS-APIRequest: true” in the header: OCS APIs overview — Nextcloud latest Developer Manual latest documentation
Can I request to add custom headers within the " Edit: Webhook" screen along side of the custom payload option.
Please use the provided template. It’s important. Thank you.
Title: Enhancement for the webhooks - Custom headers
What is your original issue/pain point you want to solve?
On a trigger action have a message sent to NextClound Group chat withing it’s Talk Application
Which are one or two concrete situations where this problem hurts the most?
Active Push Notifactins on an Action using NextCloud or other API that require custom headers on a webhook
Why is it not solvable with the Zammad standard?
No where to create custom headers.
What is your expectation/what do you want to achieve?
Allow an area to add to the header information within the “Edit: Webhook” screen
If there is any more useful information, feel free to share it all (e.g.: mockup screenshots, if something is UI related, or the API URL/documentation URL for a service you need a connection to).
https://docs.nextcloud.com/server/latest/developer_manual/client_apis/OCS/ocs-api-overview.html
Your Zammad environment:
Been testing it for a year or 2 before putting into production.
Currently: Debian 13 / Zammad version 6.1.0-1694783928.bfa2ec1e.bookworm
Any updates for this feature request? I would love the option to have custom headers.
Small input from my side, it doesnt have to be complicated for everyone that doesn’t need or use it, just keep the original UI and just add a “advanced” button, which gives you a whole new UI with those custom headers and maybe also the different authentication methods, etc.
At least different authentication method should be possible with the last release.
Completley custom headers are not implemented yet, but could maybe also be a quick win. Let’s see what the year brings.