> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/analyze/integrated-webhooks/integrated-webhooks-common-questions/integrated-webhooks-error-when-sending-webhook-possible-causes.md).

# Integrated Webhooks - Error when sending webhook - possible causes

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F6ZXcb5KmlborLdOPDTPb%2Fundraw_server_down_s4lk.png?alt=media&amp;token=671ee0aa-11e6-48ac-9f57-2248de071d84" alt=""><figcaption></figcaption></figure>

#### How do you check if your webhook is not working?

For each call, a system report is generated and turned into a chart. See the screenshots below.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FMnRoJUL7YgcDQ6IFuCOP%2F2.png?alt=media&amp;token=f2e2d667-0b6b-4155-b273-c062fd3e29a3" alt=""><figcaption></figcaption></figure>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FCSphRyd4qFk1CEsMcYBe%2F1.png?alt=media&amp;token=8bce5328-4b7e-476c-a0b7-a3b06d3dd977" alt=""><figcaption></figcaption></figure>

If these charts show no activity, it means the webhook was never called and therefore some information is missing.&#x20;

**Possible Errors Related to the Webhook:**

During the configuration and use of webhooks, several errors related to the alias and secret key may occur:

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F2kixSlG2z6zVdu2QYBhp%2F3.png?alt=media&amp;token=3e92c517-9310-499a-99b0-b60c08992890" alt=""><figcaption></figcaption></figure>

**Incorrect Alias**: If you changed the configured alias and did not update it in the platform you want to connect to, it is causing a communication error. It is necessary to check whether the Alias or the link is correct on the external platform (form, landing page, etc.).

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FUkAz2Z8Hcr7JDELRyC9G%2F4.png?alt=media&amp;token=54b8f587-9fb1-49b8-87c2-f37d5b53b15e" alt=""><figcaption></figcaption></figure>

**Invalid Secret Key**: An incorrect or outdated secret key can result in events being rejected by the destination system. This can cause failures in delivering important events and in synchronization between systems.

**Secret Key Exposure**: If the secret key is exposed, whether by accidental sharing or a data leak, unauthorized third parties may send forged or malicious events, compromising the integrity of the system.

**Fields configured incorrectly**: if you are requesting fields that do not exist in your integrated webhook, it will return an error because there are no fields to fill in.&#x20;

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2Fq4dho4lXxnOKb2g1fc6d%2F5.png?alt=media&amp;token=25960bc3-d0a0-4dc3-b096-b0a68b7f8d41" alt=""><figcaption></figcaption></figure>

**3. Resolving the Errors:**

Here are some measures to resolve these errors and ensure the proper functioning of webhooks:

* **Regular Alias Check**: Regularly check whether the configured alias matches what the destination system expects. This can be done through the integration settings screen, where you can view and modify the alias as needed.
* **Secret Key Update**: Make sure the secret key is up to date and matches the one configured in the destination system. If necessary, update the secret key in the integration settings screen to ensure proper event authentication.
* **Secret Key Security**: Keep the secret key secure and avoid exposing it unnecessarily. Limit access to the key and follow recommended security practices to protect the integrity of the system.
* **Field Mapping Review**: Check the field mapping in the webhook and in the destination system. Make sure the requested fields match the data available at the source and that the mapping is configured correctly.


---

# 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.sprinthub.com/en/topics/analyze/integrated-webhooks/integrated-webhooks-common-questions/integrated-webhooks-error-when-sending-webhook-possible-causes.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.