From a9897674b14273f59c5398015cd8904f0cf62f01 Mon Sep 17 00:00:00 2001 From: Jeremy Yeo Date: Tue, 17 Sep 2024 14:08:41 +1200 Subject: [PATCH] Update webhooks.md --- website/docs/docs/deploy/webhooks.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/website/docs/docs/deploy/webhooks.md b/website/docs/docs/deploy/webhooks.md index 10354fe5da9..38b2ae13030 100644 --- a/website/docs/docs/deploy/webhooks.md +++ b/website/docs/docs/deploy/webhooks.md @@ -551,3 +551,10 @@ DELETE https://{your access URL}/api/v3/accounts/{account_id}/webhooks/subscript - [dbt Cloud CI](/docs/deploy/continuous-integration) - [Use dbt Cloud's webhooks with other SaaS apps](https://docs.getdbt.com/guides?tags=Webhooks) +## Troubleshooting + +* If your destination system is not correctly receiving dbt Cloud webhooks - check that the system allows Authorization headers. dbt Cloud webhooks necessarily send an Authorization header and if your endpoint does not support receiving Authorization headers, then it may be incompatible with dbt Cloud webhooks. Some services like Azure Logic Apps / Power Automate may not accept Authorization headers and therefore will not work with dbt Cloud webhooks. You can test if your destination endpoint supports Authorization headers by sending a request using curl with an Authorization header - for example: + +```shell +curl -H 'Authorization: 123' -X POST https:// +```