Skip to content

Commit 06140a3

Browse files
Added a troubleshooting section for webhook (#11099)
* Added a troubleshooting section for webhook * Update docs/user/guides/build/webhooks.rst --------- Co-authored-by: Eric Holscher <[email protected]>
1 parent a096bd6 commit 06140a3

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

docs/user/guides/build/webhooks.rst

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -277,3 +277,21 @@ you can use this payload:
277277
"date": "{{ build.start_date }}"
278278
}
279279
}
280+
281+
Troubleshooting webhooks and payload discovery
282+
----------------------------------------------
283+
284+
You can use public tools to discover, inspect and test webhook
285+
integration. These tools act as catch-all endpoints for HTTP requests
286+
and respond with a 200 OK HTTP status code. You can use these payloads
287+
to develop your webhook services. You should exercise caution when using
288+
these tools as you might be sending sensitive data to external tools.
289+
290+
These public tools include:
291+
292+
- `Beeceptor <https://beeceptor.com/webhook-integration/>`__ to create
293+
a temporary HTTPS endpoint and inspect incoming payloads. It lets you
294+
respond custom response code or messages from named HTTP mock server.
295+
- `Webhook Tester <https://webhook-test.com/>`__ to inspect and debug
296+
incoming payloads. It lets you inspect all incoming requests to it’s
297+
URL/bucket.

0 commit comments

Comments
 (0)