Required roles
Process Engineer or Admin
Webhooks in AnyFleet offer an event‑driven mechanism that delivers real‑time notifications to a user‑defined HTTPS endpoint. Users can setup to receive a webhook notification whenever a key event occurs or use it as a system action to notify or receive an update from an external system.
When to use webhooks
Use a webhook to receive a real-time notification to external endpoint every time a key event occurs
Use a Webhook call system action to notify your WMS/ERP about picked or dropped resources and mission details (for more information, refer to the knowledge article System Action - Webhook Call)
Use a webhook with Dynamic Mission Update (DMU) system action to receive an update from your WMS/ERP to dynamically allocate pick up and drop off locations
Create a Webhook
Go to the “Webhooks” section in AnyFleet
Click “Add webhook” to create a new webhook
Enter the required information (endpoint URL from your external system, content type and secret)
Select the event type you want the webhook to react to (you can subscribe the webhook to listed events or leave everything unselected if you just want to use the webhook for system actions)
Save the webhook
The table below gives an explanation to the respective input fields for the webhook creation.
Field | Description | Example | Mandatory/Optional |
Name | User-definable name for this webhook. Name will be shown in overview list of all webhooks. | Demo webhook | Optional |
Endpoint | Defines the endpoint being called after an event is triggered. The endpoint must be an https address. |
| Mandatory |
Content type | Specifies the format of the content inside the body for the POST request. By default, is JSON but it can be changed to x-www-form-urlencoded. | JSON (default) | Mandatory |
Secret | The key used with HMAC-SHA-256 to hash the body and put it into the header X-AnyFleet-Signature. The consumer will verify for each request that this is the expected value to avoid man-in-the-middle attacks. Length must be between 32 and 64 byt-es. | Password between 32 and 64 bytes | Mandatory |
Event type | AnyFleet events associated and subscribe-able by a webhook. | On Emergency mode trigger | Optional |
Custom headers | Additional headers, which can be attached to the POST request. The limit is 10. | It contains Name and Value | Optional |
Disable Webhook | Option to disable the webhook, thus no payloads will be sent to the specified endpoint. |
| Optional |
Webhook Logs
In the "Webhooks" section in AnyFleet, selecting an existing webhook, a user can access last 500 webhook logs. The logs contain parameters on general information as well as the complete payload of the request, including headers and body. To support analysis and troubleshooting, each logged webhook request can be retried, regardless of failed or successful delivery. Retried requests will be marked as "Redelivery" and will use the original Delivery ID.
