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. Specifically, for the Mission resource and the Cancel operation, it allows users to cancel a mission by referencing its unique identifier. This is useful in logistics and transport management scenarios where planned missions need to be aborted or invalidated due to changes in scheduling, client requests, or operational issues.
Practical examples include:
- Canceling a delivery mission that can no longer be fulfilled.
- Aborting a transport task due to vehicle unavailability.
- Stopping a mission before it starts to avoid unnecessary costs or conflicts.
Properties
| Name | Meaning |
|---|---|
| Mission Reference | The reference string identifying the mission to cancel. Optional; if not provided, behavior depends on implementation. |
Output
The node outputs JSON data representing the result of the cancel operation on the mission. This typically includes confirmation of cancellation, updated mission status, or error details if the cancellation failed.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node uses internal API request functions to communicate with Everest's endpoints.
- No additional external services are explicitly required beyond the Everest TMS API.
Troubleshooting
Common Issues:
- Providing an invalid or empty mission reference may cause the cancellation to fail.
- Network or authentication errors when connecting to the Everest API.
- Attempting to cancel a mission that is already completed or canceled might return an error.
Error Messages:
- Errors returned from the API will be propagated as messages in the node output.
- If "Continue On Fail" is enabled, errors will be included in the output JSON under an
errorfield instead of stopping execution.
Resolutions:
- Ensure the mission reference is correct and corresponds to an existing mission.
- Verify API credentials and network connectivity.
- Check mission status before attempting cancellation to avoid invalid operations.
Links and References
- Everest TMS Official Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes
- General REST API best practices for error handling and authentication.