Everest icon

Everest

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

Actions55

Overview

The node integrates with the Everest Transport Management System (TMS) to perform various operations related to transport missions, clients, agents, invoices, and more. Specifically, for the Mission resource and the Estimate operation, it allows users to estimate details about a transport mission based on provided parameters such as service type and addresses.

This node is beneficial in scenarios where logistics or transport companies want to automate the calculation of mission estimates directly within their workflows. For example, a user can input start and end addresses along with a selected service to get an estimated cost or duration for a delivery mission without manually querying the TMS.

Practical examples:

  • Estimating the cost of a delivery from one address to another using a specific transport service.
  • Quickly obtaining route distance or time estimates before creating a full mission order.
  • Integrating mission estimation into automated booking or dispatch systems.

Properties

Name Meaning
Service The transport service to use for this mission. Options are dynamically loaded from Everest and represent available services.
Start Address The starting address for the mission. Example: "42 fake street, 75001 Paris".
End Address The destination address for the mission. Example: "42 fake street, 75001 Paris".

Output

The node outputs a JSON array containing the results of the requested operation(s). For the Mission Estimate operation, the output typically includes estimated data related to the mission such as cost, duration, distance, or other relevant metrics returned by the Everest API.

The exact structure depends on the API response but generally contains fields describing the estimate details for the mission based on the input parameters.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Everest TMS API.
  • Needs an API key credential configured in n8n for authenticating requests to Everest.
  • Uses internal methods to load options dynamically (e.g., services list).
  • The node relies on the Everest API endpoints such as /services and mission-related endpoints to fetch and send data.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing incomplete or incorrect addresses may result in errors or inaccurate estimates.
    • Selecting a service that does not support estimation could lead to empty or error responses.
    • Network connectivity problems can prevent communication with the Everest API.

  • Error messages:

    • Authentication errors: Check that the API key credential is correctly set up and valid.
    • Validation errors: Ensure all required fields (addresses, service if required) are properly filled.
    • API errors: Review the error message returned by Everest; it might indicate invalid parameters or service unavailability.

  • Resolution tips:

    • Verify API credentials and permissions.
    • Double-check input addresses for correctness and completeness.
    • Use the dynamic dropdowns to select valid services.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.

Links and References

Discussion