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 on multiple resources such as missions, clients, agents, invoices, and more. Specifically, for the Mission - Accept operation, this node allows an agent to accept a mission by referencing the mission and optionally specifying the accepting agent.

This node is beneficial in workflows where transport missions need to be programmatically managed, such as automatically assigning or accepting missions based on business logic or external triggers. For example, when a new mission is created in Everest TMS, this node can be used to accept that mission on behalf of a specific agent, streamlining dispatch processes.

Properties

Name Meaning
Mission Reference The reference identifier of the mission to accept.
Agent The agent who will accept the mission. Options are dynamically loaded from available agents.

Output

The node outputs a JSON array containing the result(s) of the accept mission operation. Each item in the output corresponds to the response from the Everest TMS API after attempting to accept a mission. The structure typically includes details about the accepted mission, confirmation status, or any relevant metadata returned by the API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Everest TMS API.
  • The node depends on the Everest TMS REST API endpoints to fetch agents and perform mission acceptance.
  • Dynamic options such as the list of agents are loaded via API calls within the node.
  • Proper configuration of the Everest API credentials in n8n is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing mission reference may cause the API call to fail.
    • Specifying an agent ID that does not exist or is not authorized could lead to errors.
    • Network or authentication issues with the Everest API will prevent successful execution.

  • Error Messages:

    • Errors returned from the Everest API will be propagated. Common messages might include "Mission not found," "Agent not authorized," or "Invalid credentials."
    • If the node is set to continue on failure, error messages will appear in the output JSON under an error field.

  • Resolution Tips:

    • Verify the mission reference string is correct and corresponds to an existing mission.
    • Ensure the selected agent is valid and has permission to accept missions.
    • Confirm that the Everest API credentials are correctly configured and have sufficient permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion