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, for the Mission - Get operation, it retrieves details of a mission by its reference identifier.
Typical use cases include:
- Fetching detailed information about a specific transport mission in your logistics workflow.
- Automating retrieval of mission data to update dashboards or trigger further processing.
- Integrating mission data into other systems or workflows for reporting or operational purposes.
Example: You can use this node to get the status and details of a shipment mission by providing its unique reference, then use that data to notify stakeholders or update your internal tracking system.
Properties
| Name | Meaning |
|---|---|
| Mission Reference | The reference string identifying the mission to retrieve. Optional; if omitted, behavior depends on implementation (likely fetches multiple or errors). |
Output
The node outputs JSON data representing the mission(s) retrieved from Everest TMS. The structure typically includes all relevant mission details such as identifiers, status, assigned agents, routes, timings, and other metadata related to the transport mission.
If multiple missions are returned (depending on input), the output is an array of mission objects.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node internally calls the Everest API endpoints to perform operations.
- No additional external dependencies beyond the configured Everest API credentials.
Troubleshooting
Common issues:
- Providing an invalid or empty mission reference may result in no data or an error.
- Network or authentication failures will cause the node to throw errors.
- If the mission does not exist or is inaccessible, the API may return an error or empty response.
Error messages:
- Errors from the Everest API will be propagated; typical messages might include "Mission not found" or "Unauthorized".
- To resolve, verify the mission reference is correct and the API credentials are valid.
- Ensure network connectivity to the Everest API endpoint.
Continue On Fail:
- If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.
Links and References
- Everest TMS Official Documentation (example placeholder link)
- n8n documentation on Creating Custom Nodes
- General REST API usage best practices for authenticated requests
Note: This summary is based solely on static analysis of the provided source code and property definitions.