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 Everest TMS (Transport Management System) to perform various operations on different resources such as missions, clients, agents, invoices, and more. Specifically, the "Get Many by References" operation under the "Mission" resource allows users to retrieve multiple mission records by specifying their references in a comma-separated string.
This operation is useful when you have a list of mission identifiers and want to fetch detailed information about all those missions in one go. For example, logistics coordinators can use this to quickly gather status updates or details for several transport missions they are managing.
Properties
| Name | Meaning |
|---|---|
| Mission References | Comma-separated list of mission reference strings identifying the missions to retrieve. |
Output
The output is a JSON array where each element corresponds to a mission object retrieved from Everest TMS based on the provided references. Each mission object contains detailed data fields representing the mission's attributes as returned by the Everest API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to Everest TMS via an API key credential configured in n8n.
- The node uses the Everest API endpoints internally to fetch mission data.
- No additional external dependencies beyond the Everest API and its authentication.
Troubleshooting
- Empty or invalid mission references: If the input string is empty or contains invalid references, the node may return an empty array or error messages. Ensure that mission references are correctly formatted and exist in Everest TMS.
- API authentication errors: If the API key credential is missing, expired, or incorrect, the node will fail to authenticate. Verify the API key configuration in n8n credentials.
- Rate limiting or network issues: Temporary failures communicating with Everest API might cause errors. Retrying or checking network connectivity can help.
- Error messages: Errors thrown by the node typically include the message from the Everest API response. Review these messages to identify issues such as permission problems or invalid parameters.
Links and References
- Everest TMS Official Website
- Everest TMS API Documentation (Assumed link; replace with actual if available)