> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/send-view-updates-to-webhooks.md).

# Send View updates to Webhooks

**New Activations of this feature will be Disabled as of December 25, 2025.**

{% hint style="warning" %}
Note: This is a custom feature that is not enabled by default
{% endhint %}

HockeyStack allows for you to send hourly updates from created Views to custom Webhooks. To configure this, go a view and open the filter settings. 

Open configuration settings by clicking "Configure" next to "Send Alerts".  

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2F6nppreO3WlBcAzC8WaQh%2FScreenshot%202025-01-14%20at%2012.31.54%E2%80%AFPM.png?alt=media&amp;token=4bda1717-0139-43fe-9199-12cc7c6f486a" alt="" width="375"><figcaption></figcaption></figure>

That will open the Send Alerts menu, which will show options to send alerts to Slack and Webhooks. (Depending on what you have activated.)&#x20;

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FyfTB3A9qLJmdx9Zsys8o%2FScreenshot%202025-01-14%20at%2012.36.03%E2%80%AFPM.png?alt=media&amp;token=a320ff29-bb62-4d40-a811-a494d83f6dcb" alt="" width="375"><figcaption></figcaption></figure>

Add a new webhok, and fill in the required information.&#x20;

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2F3RNugR0xeT8GjzCrYTPn%2FScreenshot%202025-01-14%20at%2012.38.19%E2%80%AFPM.png?alt=media&amp;token=f4a1010a-9960-4e8e-b825-d5fda81d2930" alt="" width="375"><figcaption></figcaption></figure>

* **Webhook Name** is a title for your Webhook, defined by you.
* **Webhook URL** is the URL of the webhook, starting with either http\:// or https\://
* Headers&#x20;
  * "Content-Type" is included by default, to fit in line with how data is sent to the webhook
  * Some webhooks may require other headers for authentication, so those such as "Authorization" can be added in here as well

Once you're finished, you can add the webhook, and see it listed in the Send Alerts menu:&#x20;

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FZrBua7l5rEP0afaZ0Yqp%2FScreenshot%202025-01-14%20at%2012.44.59%E2%80%AFPM.png?alt=media&amp;token=07f56dd1-7475-4603-b2a4-f72e1e828f89" alt="" width="375"><figcaption></figcaption></figure>

Now, updates will be sent hourly to that webhook.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hockeystack.com/marketing-intelligence/send-view-updates-to-webhooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.