Integrated Webhooks - Error sending webhook - possible causes

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.

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

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:

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.).

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.

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.