Everest icon

Everest

Interact with Everest TMS (Transport Management System)
Join our community

Actions55

Overview

The "Everest" node integrates with the Everest Transport Management System (TMS) to perform various operations across multiple resources such as General, Mission, Client, Agent, Invoice, Contact, Alert, Walter, Notification, Webhook, Route, and Export.

Specifically, for the General resource and the Get Availabilities operation, this node fetches availability data filtered optionally by establishment or search terms. This is useful in scenarios where you need to retrieve available services, skills, or areas of service within a specific establishment or matching certain criteria.

Practical examples include:

  • Retrieving available driver skills filtered by a keyword.
  • Getting available services offered at a particular establishment.
  • Listing availabilities to schedule missions or assign agents efficiently.

Properties

Name Meaning
Options A collection of optional filters to refine the query results.
├─ Search (Only for "getSkills" operation) A search term string to filter skill names (e.g., "driving").
└─ Establishment (For "getServices", "getAreasOfService", "getAvailabilities") Select an establishment to filter results by its ID. The list is dynamically loaded from available establishments.

Output

The node outputs a JSON array containing the requested availability data. The exact structure depends on the operation but generally includes lists of services, skills, areas of service, or availabilities with their respective details such as IDs, names, descriptions, and related metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential to authenticate requests against the Everest TMS API.
  • Uses internal methods to load options dynamically (e.g., establishments, services, skills).
  • The node relies on the Everest API endpoints such as /services, /skills, /establishments via POST requests.

Troubleshooting

  • Empty results: If no availabilities are returned, verify that the establishment ID or search term filters are correct and that the Everest system contains relevant data.
  • Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Load options failures: Dynamic loading of establishments or other options may fail if the API is unreachable or credentials are invalid.
  • Error messages: Errors thrown during execution will be shown unless "Continue On Fail" is enabled, in which case error messages are included in the output JSON under an error field.

Links and References

Discussion