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. Specifically, the Client - Delete operation allows users to delete a client record by specifying its unique Client ID. This is useful in scenarios where client data needs to be removed from the system, such as when a client relationship ends or data cleanup is required.
Practical examples:
- Removing a client who has canceled all services.
- Cleaning up test or duplicate client entries.
- Automating client lifecycle management by deleting clients after certain conditions are met.
Properties
| Name | Meaning |
|---|---|
| Client ID | The ID of the client to delete. |
The "Client ID" property is a required numeric input that identifies which client record will be deleted.
Output
The node outputs a JSON array containing the result of the delete operation for each input item processed. Typically, this output will include confirmation of deletion or any relevant response from the Everest TMS API.
If an error occurs and "Continue On Fail" is enabled, the output will include an object with an error field describing the issue.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to Everest TMS via an API key credential configured in n8n.
- The node uses the Everest API endpoints internally to perform operations.
- No additional external dependencies beyond the Everest API and proper authentication.
Troubleshooting
Common issues:
- Invalid or missing Client ID: Ensure the Client ID provided exists and is correct.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check connectivity and Everest TMS service status.
Error messages:
"Client not found": The specified Client ID does not exist; verify the ID."Unauthorized"or"Authentication failed": Check API credentials.- Other API errors will be passed through; enabling "Continue On Fail" can help handle these gracefully.
Links and References
- Everest TMS official documentation (for API details): [Not provided in source]
- n8n documentation on creating and using API credentials: https://docs.n8n.io/credentials/
- General info on Transport Management Systems: https://en.wikipedia.org/wiki/Transportation_management_system