EverestInstall

Overview

This node integrates with the Everest Transport Management System (TMS) to perform various operations on different resources such as contacts, clients, missions, invoices, and more. Specifically, for the Contact resource with the Delete operation, it allows users to delete a contact by specifying its unique ID.

Common scenarios where this node is beneficial include automating contact management workflows within Everest TMS, such as removing outdated or incorrect contact entries programmatically as part of larger automation processes.

Practical example:
A logistics company uses n8n to automate their transport management tasks. When a contact (e.g., a client representative) leaves the company, the workflow triggers this node to delete that contact from Everest TMS automatically, ensuring the system stays up-to-date without manual intervention.

Properties

Output

The node outputs a JSON array containing the response from the Everest TMS API after attempting to delete the specified contact. 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 active connection to Everest TMS via an API key credential configured in n8n.
• The node relies on the Everest TMS API endpoints to perform operations.
• Proper permissions are needed on the Everest TMS account to delete contacts.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent Contact ID will likely result in an error from the API indicating the contact was not found.
  • Insufficient permissions or expired API credentials can cause authentication errors.
  • Network connectivity problems may prevent the node from reaching the Everest TMS API.

• Error messages:

  • "Contact not found": Verify the Contact ID is correct and exists in Everest TMS.
  • "Authentication failed" or similar: Check that the API key credential is valid and has not expired.
  • "Request timed out" or network errors: Ensure stable internet connection and that Everest TMS API is reachable.

Resolving these usually involves verifying input parameters, refreshing credentials, and checking network status.

Links and References

• Everest TMS official API documentation (refer to your Everest TMS provider for access)
• n8n documentation on creating and using API credentials
• General REST API best practices for error handling and authentication