# Support for Headers and Body in Webhooks

**URL:** <https://forum.ghost.org/t/support-for-headers-and-body-in-webhooks/16573>\
**Category:** Using Ghost\
**Created:** [August 18, 2020, 6:30am UTC](https://forum.ghost.org/t/support-for-headers-and-body-in-webhooks/16573 "2020-08-18T06:30:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![valtism](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/valtism/32/9331_2.png) [@valtism](https://forum.ghost.org/u/valtism)\
**Post date:** [August 18, 2020, 6:30am UTC](https://forum.ghost.org/t/support-for-headers-and-body-in-webhooks/16573/1 "2020-08-18T06:30:18Z")

</div>

Hi folks 👋

I’ve just been using Ghost’s Webhooks for the first time. Since I am using Ghost as a headless CMS, I use them to trigger a build action on Github to redeploy my ghost site on Github Pages.

Unfortunately, this was not so simple. Ghost’s Webhooks only allow you to provide a url to ping, while Github’s actions require a POST with an authorisation header, as well as a JSON body to specify the target branch.

I eventually had to set up a server that acts as a relay - taking the Webhook from Ghost and forwarding it along with the necessary headers to Github to trigger the action. This is obviously less than ideal, and would be a lot easier if Webhooks supported headers and body in the request.

Thanks 😊

---

<div class="post-metadata">

**Author:** ![abelmark](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/abelmark/32/10476_2.png) [@abelmark](https://forum.ghost.org/u/abelmark)\
**Post date:** [November 23, 2020, 5:42pm UTC](https://forum.ghost.org/t/support-for-headers-and-body-in-webhooks/16573/2 "2020-11-23T17:42:55Z")

</div>

I’m about to implement the same functionality. I came to the same conclusion that I would have to spin up a server to act as a proxy. This seems less than ideal.
