> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/data-and-integrations/webhooks/testing-the-webhook.md).

# Testing the Webhook

### Test Record

You can select a record from the database (obviosuly of the same type as the trigger entity) that will be sent as the payload when using the 'Test' action.

### Running a Test

We highly recommend a webhook testing service like Webhook.site to send test requests, allowing you to observe the headers and payload in real time.

<figure><img src="/files/oizh7dcLjv7mr6nZesjv" alt=""><figcaption></figcaption></figure>

### JSON Payload

The shape of the JSON payload is the full record.  You can either observe the payload in a testing service like Webhook.site, or refer to the API documentation for the entity in question - the API request/response formats are exactly the same as those for webhooks.

### Test Results

After running a test, results can be viewed in the 'History' tab


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.pakk.io/data-and-integrations/webhooks/testing-the-webhook.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.