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 - Delete operation, it allows users to delete a mission by specifying its reference identifier.
Typical use cases include automating transport management workflows where missions need to be programmatically removed from the system, for example:
- Removing canceled or obsolete transport missions.
- Cleaning up test or temporary missions in bulk.
- Integrating with other systems that trigger mission deletions based on external events.
Properties
| Name | Meaning |
|---|---|
| Mission Reference | The reference string identifying the mission to delete. This is optional but typically required to specify which mission to delete. |
Output
The node outputs a JSON array containing the result of the delete operation for each input item processed. Each element in the output corresponds to one input and contains either:
- Confirmation or details about the deleted mission if successful.
- An error message object if the deletion failed and "Continue On Fail" is enabled.
No binary data output is produced by 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 environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Providing an invalid or empty mission reference will likely cause the API to return an error.
- Network or authentication failures can prevent the node from connecting to Everest TMS.
- If multiple items are processed and one fails, enabling "Continue On Fail" will allow subsequent items to process; otherwise, execution stops at the first error.
Error messages:
- Errors returned from the Everest API will be surfaced as error messages in the node output or thrown exceptions.
- Typical errors might include "Mission not found" or "Unauthorized access".
Resolutions:
- Verify the mission reference is correct and exists in the system.
- Ensure the API key credential is valid and has sufficient permissions.
- Check network connectivity and endpoint availability.
Links and References
- Everest TMS official documentation (not provided here, please refer to your Everest TMS API docs).
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/creating-nodes/