> 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/setting-up-a-webhook.md).

# Setting Up a Webhook

Create a new webhook by going to `Setup > Webhooks > Create New`

Give your webhook a name - this is internal only, and serves for you to be able to identify the function of the webhook in the future.  A good name might be something like 'Send Orders to Warehouse'

### Trigger Entity and Event

The first think you need to decide is what triggers the execution of this webhook.  Pakk supports triggering webhooks on both creation and update of \*any\* record type in the Pakk system (e.g. Order, Purchase Order, Return, Expense).

### Enable

You can work on, and test, your webhook without it actually triggering when the trigger condition is met.  Once you're ready to 'go live' with the webhook, simply enable it.


---

# 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/setting-up-a-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.
