> For the complete documentation index, see [llms.txt](https://docs.bird.com/pusher/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/pusher/channels/channels/troubleshooting/how-can-i-debug-my-channels-webhooks.md).

# How Can I Debug My Channels Webhooks?

Developing and testing WebHooks triggered from a hosted service like Pusher can be tricky. But there are a number of tools that can help you.

#### Was the WebHook triggered?

The best way to check if a WebHook was actually triggered is to look at the [Pusher Debug Console](https://pusher.com/docs/channels/getting_started/debugging#pusher_debug_console). It will tell you:

1. If the WebHook was triggered
2. What the HTTP status code was from the WebHook endpoint

#### Capturing WebHooks

There are a few handy tools that you can use to simply capture HTTP requests. These are very useful when working with WebHooks. For example, 

* <https://requestbin.com/>
* <https://webhook.site/>

#### Developing locally

The best solution for allowing WebHooks from Pusher to access your local development server it so use [ngrok](https://ngrok.com/). It provides you with a public URL that you can set as your WebHook endpoint and proxies the WebHook call to your local development server.

#### Feedback

If you find another tool or have any tricks & tips that make developing with WebHooks easier please drop an email to <support@pusher.com> or [click here](https://messagebird.com/support-center/Pusher-request-new)

{% hint style="info" %}
Still have questions? Please reach out to our Support team by visiting [this page](https://messagebird.com/support-center/Pusher-request-new).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bird.com/pusher/channels/channels/troubleshooting/how-can-i-debug-my-channels-webhooks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.