# Integrated Webhooks - Error sending webhook - possible causes

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

#### How to check if your webhook is not working?

With each call a system report is made which is transformed into a chart. see the screenshots below.

<figure><img src="/files/147da5ed45682a79353f9197a7c46c74b3c833cb" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/0b583eed044db15ee8021ff573d95f87d2b61f8d" 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, various errors related to the alias and the secret key may arise:

<figure><img src="/files/66ba5ac93e7cc69a171f86a25722ee9eca26479f" alt=""><figcaption></figcaption></figure>

**Incorrect Alias**: If you changed the configured alias and did not update it on the platform you want to connect, this will cause a communication error. You need to verify whether the Alias or the link is correct on the external platform (form, landing page, etc.).

<figure><img src="/files/6f7521b32a64048653de47147ca7d9121692d33d" 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.

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

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

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

**3. Resolving the Errors:**

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

* **Regular Alias Verification**: Regularly check that the configured alias matches what the destination system expects. This can be done through the integration configuration screen, where it is possible to view and modify the alias as needed.
* **Updating the Secret Key**: Ensure 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 configuration screen to ensure correct authentication of events.
* **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.
* **Review of Field Mapping**: Check the field mapping in the webhook and in the destination system. Ensure that the requested fields correspond to the data available at the source and that the mapping is configured correctly.


---

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