Hi @JG_520 my understanding is that unfortunately customization of workflow webhooks is extremely limited, so I’m not aware of a way to include additional headers.
I did post an update however on how to include the API key. I included screenshots on how to save the key as a secret and include in the webhook. You need to save the key in your secrets as the exact value required in the header and then select ‘API Key’ in the dropdown selection under ‘Authentication type’. Once selected, you’ll then need to actually rename the API key name to “Authorization” (as per my screenshots in the thread here: https://community.hubspot.com/t5/APIs-Integrations/Webhooks-in-Workflows-how-to-include-the-authorization-header/m-p/751928/highlight/true#M61134).
Other than that, as far as I’m aware, the only way around it is to either send the request outside of Hubspot and use something like Zapier. Or alternatively if you have Ops Hub, then you might need to see if you can use an Custom Code action step.
I’d love to see if there are improvements coming though or if anyone has a workaround solution as 99% of the time, if I’m trying to retreive information, I can’t use a webhook step in a workflow because most of them need a dynamic url or some level of customization in the request body.