Hit this button too as I really need this for my dynamic routes in next js. I have two levels of dynamic routing, when updating child page, i can not get my related mother page slug as it returns mother_page: { count: 1 }. This field from my child dynamic page is a oneToOne relation with my mother page model. I don't get why this subject is not more taken in account seriously. It lasts several years here and is critical to create a webhook that fits usual use cases.

Trying to be constructive here in the face of radio silence from the Strapi team. I have just hit this (like others, wanting to trigger a GitHub Action). I see a few solutions online (unmaintained GitHub plugins which may work but unmaintained is worrying and ChatGPT suggested a Lambda or Strapi middleware) and was wondering what people are actually doing to get around this. It could be a stretch, but it doesn't feel like this should be too difficult to implement in Strapi core. Grateful for any insight.

Please, the webhooks are useless without this

Just adding my voice here too, was wanting to trigger a Github Action but without being able to add an to the payload it is impossible

Would love to see movement on this at some point - trying to add Slack integration with webhooks, and requires a body in the request, so as far as I can tell, will never work without being able to add a body to these webhooks.

I would really like this as well! I want to be able to customize the payload or get more information, such as the user id or the role of the user who creates an article, so I can notify an admin that someone published a draft, etc.

My turn to run into this issue. As is since I'm not able to get objects related to the created/updated/deleted object the only option should be a full site build.

I have a schema of tracks and playlists. Updating a track should include all playlists it's on in the webhook call so those pages can be invalidated.

Any updates on this Derrick Mehaffy? I'm aware Strapi already appends a payload to webhook's body, but there should be a way we can customize it, or completely override it with our own payload?

I was quite surprised when I found out this wasn't supported out of the box. Original issue in Github was created in 2020, is there a concern on implementing this on the maintainers side I wonder.

Webhooks are completely pointless without this. Every system we might send an event _to_ requires at least some specific fields to be present in the request body (_sometimes_ with an additional element for 'customer data') for it to be processed. What exactly are the Strapi devs expecting we're sending a webhook to?

I'm going to have to investigate some sort of glue app/sidecar container just to be able to receive requests from Strapi, convert them into an actually useful format, and then forward them on to other systems.