From f4344d7f9b319f3ef7dc97341faca6ec14b613d7 Mon Sep 17 00:00:00 2001 From: mmahacek Date: Wed, 3 Jan 2024 11:44:12 -0800 Subject: [PATCH] Update docs/integrations/webhooks.md Co-authored-by: Jeff Gehlbach --- docs/integrations/webhooks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/webhooks.md b/docs/integrations/webhooks.md index 6ea1a8edf..4486e2e45 100644 --- a/docs/integrations/webhooks.md +++ b/docs/integrations/webhooks.md @@ -109,5 +109,5 @@ Content-Type: application/x-www-form-urlencoded Note that `webhook_receiver` does not actually _do_ anything with the information received: It merely prints the request headers and body for inspection. Now, when the NetBox webhook is triggered and processed, you should see its headers and content appear in the terminal where the webhook receiver is listening. If you don't, check that the `rqworker` process is running and that webhook events are being placed into the queue. -Webhook results can be found in the NetBox admin UI under the Background Tasks section. +Webhook results can be found in the NetBox admin UI under the Background Tasks section. Webhook results can be found in the NetBox admin UI under the Background Tasks section. You can see any finished or failed runs, as well as the error stack if the webhook failed.