Actions55
- Client Actions
- General Actions
- Mission Actions
- Agent Actions
- Invoice Actions
- Contact Actions
- Alert Actions
- Walter Actions
- Notification Actions
- Webhook Actions
- Route Actions
- Export Actions
Overview
The Everest node integrates with the Everest Transport Management System (TMS) to automate and manage various transport-related workflows. Specifically, the Webhook - Subscribe operation allows users to register a webhook URL to receive real-time notifications for specific events occurring within the Everest platform.
This is beneficial in scenarios where you want to trigger automated workflows or synchronize data based on changes or actions in Everest without polling the API continuously. For example, you can subscribe to "Mission Created" events to automatically start processing new transport missions as soon as they are created, or listen for "User Updated" events to keep your user database in sync.
Practical examples:
- Automatically update your CRM when a client is created or updated.
- Trigger alerts or notifications when a mission status changes.
- Sync agent location updates to a live tracking dashboard.
Properties
| Name | Meaning |
|---|---|
| Webhook URL | The URL endpoint where Everest will send webhook notifications for the subscribed event. |
| Event | The specific event to subscribe to. Options include: Backend Auth, User Created/Updated/Deleted, Mission Created/Updated/Deleted/Cancelled/Finished/Failed/Success/Picked Up/Dispatched/Status Changed/Rescheduled/Price Updated, Missions Imported, Client Created/Updated/Deleted/Tariffs Updated/API Updated, Agent Created/Updated/Location Updated/Deleted/File Created/Updated/Deleted, Invoice Created/Updated/Deleted, Refund Created, Contact Created/Updated/Deleted, Comment Created/Updated, Service Created/Updated, Status Created/Updated, Vehicle Created/Updated, Platform Global Settings Updated/Invoicing Updated, Area of Service Created/Updated, Tariff Policy Updated, Dispatch Rules Updated, Role Created/Updated, Availabilities Updated, Establishment Created/Updated/Deleted, Form Created/Updated, Support Email Sent. |
Output
The node outputs an array of JSON objects representing the result of the subscription request. Typically, this includes confirmation details about the webhook subscription such as subscription ID, status, or any metadata returned by the Everest API.
If the node supports binary data output (not indicated here), it would represent raw webhook payloads or files related to the subscribed events.
Dependencies
- Requires an active connection to the Everest TMS API.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- The webhook URL must be publicly accessible to receive incoming HTTP POST requests from Everest.
Troubleshooting
Common issues:
- Invalid or unreachable webhook URL: Ensure the URL is correct and publicly accessible.
- Insufficient permissions: Verify that the API credentials have rights to manage webhook subscriptions.
- Event name mismatch: Confirm the event selected matches one supported by Everest.
- Network connectivity problems between Everest and your webhook endpoint.
Error messages:
"Invalid webhook URL": Check the URL format and accessibility."Unauthorized"or"Authentication failed": Recheck API credentials."Event not found": Select a valid event from the provided options.- Timeout errors: Ensure your webhook endpoint responds quickly to avoid retries or failures.
Resolving these typically involves verifying configuration settings, network access, and ensuring the webhook endpoint correctly handles incoming requests.
Links and References
- Everest TMS official API documentation (for webhook events and subscription management)
- n8n webhook usage guide
- General webhook best practices and security considerations