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
This node integrates with the Everest Transport Management System (TMS) to perform various operations on different resources such as routes, missions, clients, agents, invoices, and more. Specifically, for the Route - Get operation, it retrieves detailed information about a single route identified by its unique Route ID.
Typical use cases include:
- Fetching route details to display or process in workflows.
- Integrating route data into logistics or transport automation pipelines.
- Validating or auditing route information before further processing.
For example, you might use this node to get the details of a specific delivery route by providing its Route ID, then use that data to update shipment statuses or trigger notifications.
Properties
| Name | Meaning |
|---|---|
| Route ID | The unique numeric identifier of the route to retrieve. This is required for the Get operation. |
Output
The node outputs an array of JSON objects representing the retrieved route(s). Each object contains detailed information about the route corresponding to the provided Route ID. The exact structure depends on the Everest TMS API response but typically includes fields such as route identifiers, associated stops, timings, status, and related metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Everest TMS API.
- Needs an API authentication credential configured in n8n to authorize requests.
- The node internally calls a helper function to send POST requests to the Everest API endpoints.
- No additional external dependencies beyond the Everest API and proper credentials.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Route ID will likely result in an error or empty response.
- Network connectivity problems or incorrect API credentials can cause authentication failures.
- If the Everest API changes or is temporarily unavailable, requests may fail.
Error messages:
- Errors returned from the API are caught and can be output if "Continue On Fail" is enabled.
- Typical errors include "Route not found", "Unauthorized", or "Internal server error".
Resolutions:
- Verify the Route ID exists and is correct.
- Check that the API key or authentication token is valid and has necessary permissions.
- Ensure network access to the Everest API endpoint.
- Enable "Continue On Fail" to handle errors gracefully within workflows.
Links and References
- Everest TMS official API documentation (refer to your Everest TMS provider for exact URLs).
- n8n documentation on creating and using API credentials.
- General REST API best practices for troubleshooting connectivity and authentication issues.