Hi, this question is directed to Prismic Support. I'm attempting to connect a Prismic webhook to Azure DevOps so I can trigger a pipeline run when a CMS user publishes a document, for example. I am able to get the webhook up and running, and it seems to trigger pipeline when I manually click the "Trigger It" button in Settings/Webhooks. However, when I go to publish/unpublish the document, I receive a 200 response but nothing is triggered in DevOps. Can you help me sort this out?
Welcome to the Prismic community and thanks for reaching out to us.
The following thread might be related to your thread. Could you please check this: Webhook API Build Trigger Broken
Hi @Priyanka , thank you for sharing that thread. Unfortunately I am unable to implement the workaround that was suggested because I don't have access to Azure Logic Apps in my environment. It sounds like the root cause is that Prismic is sending a webhook trigger with JSON in the body that breaks something on the Microsoft side, where I need just a clean POST sent from Prismic (which is exactly how the manual trigger is set up).
So to summarize, I need a way for Prismic to send exactly the same POST request on publish/unpublish of release or documents as the manual trigger (i.e. with no JSON body). How can I configure this?
I apologize for the delayed response.
There's no way to send an empty request body with Prismic.
I found another user who deployed a Next.js app on the Digital Ocean App Platform and added an API endpoint in their app to receive the webhook, format it, and forward the request to Digital Ocean. That could be an option.
Ok I see, thanks. It's hard to tell whether this is an issue on the Prismic side or Microsoft side, so I'll go ahead and open a ticket with Microsoft on this as well.