A webhook is configured but no requests are appearing in the history log, or the external system is not receiving data.
Webhook not assigned to an Alert Rule
A webhook created in Company Settings does not send requests on its own. It must be assigned as a notification action on at least one Alert Rule in a Kio App. If no Alert Rule has this webhook assigned, no requests are sent regardless of app activity.
- Open the relevant Kio App (for example, Staff Safe or Asset Tracker) from the Kontakt.io Launchpad.
- Go to Alert Rules.
- Edit an existing rule or create a new one.
- In the Actions section, select Webhook and assign this webhook.
- Save the Alert Rule, then trigger a test alert to confirm the webhook request is sent.
Wrong app selected on the webhook
The Apps field controls which Kio Apps' Alert Rules can assign the webhook. If the correct app is not selected, the webhook does not appear as an option in that app's Alert Rules.
- Open Company Settings and select Webhooks.
- Open the webhook and select Edit.
- Under Apps, confirm the app whose Alert Rules you are trying to assign this webhook from is selected.
- Save, then return to the Alert Rule in the app to assign the webhook.
Kio App not active on the account
If the Kio App is not activated on the account, its Alert Rules cannot be triggered and no webhook requests are sent.
- Confirm the Kio App is listed on the Kontakt.io Launchpad.
- If it is not listed, submit a support request to have the app activated.
URL is incorrect or unreachable
If the webhook URL is wrong or the external system is not publicly accessible, requests will fail.
- Open the webhook and verify the URL.
- Check the History log tab for failed requests; look for 4xx or 5xx status codes.
- Select a failed request to view the full response for more detail.
- Confirm the external system is reachable from the internet.
Variable syntax error in the payload
A variable reference that does not match an existing variable can cause the payload to fail or send an empty value.
- In the webhook payload, confirm every variable reference matches an existing variable name in the Variables tab.
- Check the History log request body to confirm the payload was sent correctly.
Authentication failing on the external system
If the external system requires authentication and the credentials are incorrect, it will return a 4xx response.
- In the History log, select a failed request and check the status code and response body.
- Confirm the authentication header or URL parameter is set correctly on the webhook.
- If using a Secret variable for a token, recreate the variable to confirm the value is correct — Secret variable values cannot be viewed after saving.