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 the Everest Transport Management System (TMS) API, allowing users to perform various operations on different resources such as missions, clients, agents, invoices, contacts, alerts, notifications, webhooks, routes, and exports.
Specifically, for the Route - Delete operation, the node deletes a route identified by its Route ID from the Everest TMS. This is useful in scenarios where a planned or existing route needs to be removed from the system, for example, if a delivery route is canceled or no longer valid.
Practical examples:
- Removing obsolete or incorrect routes from the transport management workflow.
- Cleaning up routes after completion or cancellation of shipments.
- Automating route management by deleting routes based on certain conditions in a workflow.
Properties
| Name | Meaning |
|---|---|
| Route ID | The numeric identifier of the route to delete. This is a required field. |
Output
The node outputs a JSON array containing the result of the delete operation for each input item processed.
- The
jsonoutput typically contains confirmation of the deletion or details about the deleted route. - If multiple items are processed, the output will be an array of such results.
- The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node uses the Everest API endpoints internally to perform operations.
- No additional external dependencies beyond the configured API credentials.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Route ID will likely cause the API to return an error.
- Network or authentication failures can prevent successful communication with the Everest API.
- Missing or incorrect API credentials will cause authorization errors.
Error messages:
- Errors returned from the Everest API will be propagated. For example, "Route not found" if the Route ID does not exist.
- Authentication errors if the API key is invalid or missing.
Resolutions:
- Verify that the Route ID exists and is correct.
- Ensure the API key credential is properly configured and has necessary permissions.
- Check network connectivity and endpoint availability.
Links and References
- Everest TMS official API documentation (not provided here; consult your Everest TMS provider)
- n8n documentation on creating and using API credentials
- General REST API best practices for error handling and authentication