HubSpot’s webhook action on workflows can’t send custom headers beyond authentication.
In 2026, so many APIs require additional headers for versioning, routing or validation. Right now, if your target API needs anything beyond Authorization, you can’t use the webhook action in workflows.
The fix is simple: add a “Custom Headers” section to the webhook action exactly like the request body mapping that already exists. Let us add key/value header pairs.
This isn’t a nice-to-have. It’s a glaring omission that forces paying Enterprise customers to route around HubSpot’s basic tooling. Please prioritize this.