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
The 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 "Mission" resource includes an operation called "Mark as Seen," which allows users to mark a mission as viewed or acknowledged within the system.
This node is beneficial in workflows where tracking the status of transport missions is important—for example, automating updates when a mission has been reviewed by a user or system component. Practical use cases include logistics companies wanting to automate mission status updates or trigger downstream processes once a mission is marked as seen.
Properties
| Name | Meaning |
|---|---|
| Mission Reference | The reference identifier of the mission to mark as seen. This is a string value that specifies which mission to update. It is optional but typically required to identify the target mission. |
Output
- The output is a JSON array containing the results of the executed operation(s).
- For the "Mark as Seen" operation on a mission, the output JSON will likely contain confirmation details or the updated mission data indicating it has been marked as seen.
- The node does not explicitly handle binary data outputs.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node depends on the Everest TMS service endpoints to perform operations.
- No additional external dependencies are indicated beyond the configured API authentication.
Troubleshooting
Common Issues:
- Providing an invalid or empty mission reference may cause the operation to fail because the system cannot identify which mission to mark as seen.
- Network or authentication errors if the API key is missing, expired, or incorrect.
- If the mission does not exist or is already marked as seen, the API might return an error or no change.
Error Messages:
- Errors returned from the Everest API will be surfaced, often including messages about invalid references or permission issues.
- To resolve, verify the mission reference input, ensure valid API credentials, and confirm the mission exists in the system.
Links and References
- Everest TMS Official Documentation (example placeholder, replace with actual URL if available)
- n8n documentation on Creating Custom Nodes