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 interacts with the Everest Transport Management System (TMS) API to perform various operations on different resources, including Agents. Specifically, for the Agent Delete operation, it deletes an agent identified by a given Agent ID from the Everest system.
Typical use cases include automating the removal of agents who are no longer active or needed in the system, cleaning up test data, or integrating agent management workflows into broader automation pipelines.
For example, you might use this node to delete an agent after their contract ends, triggered automatically by your HR system or another workflow.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique numeric identifier of the agent to delete. This is required to specify which agent should be removed from the system. |
Output
The node outputs a JSON array containing the response from the Everest API after attempting to delete the specified agent. The exact structure depends on the API's response but typically includes confirmation of deletion or error details if the operation failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the Everest TMS API.
- The node relies on the Everest API endpoints and expects network connectivity to the Everest service.
- No additional external dependencies beyond the configured API credentials and internet access.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Agent ID will likely result in an error from the API indicating the agent was not found.
- Missing or incorrect API credentials will cause authentication failures.
- Network issues or API downtime can lead to request timeouts or connection errors.
Error messages:
"Agent not found": Verify that the Agent ID exists in the Everest system."Authentication failed": Check that the API key credential is correctly set up and valid."Request timeout"or"Network error": Ensure stable internet connection and that the Everest API endpoint is reachable.
To resolve these, confirm the input Agent ID is correct, verify API credentials, and check network connectivity.
Links and References
- Everest TMS official API documentation (refer to your internal or vendor-provided docs)
- n8n documentation on setting up API credentials and using HTTP-based nodes