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 clients, missions, agents, invoices, and more. Specifically, the Client - Get operation retrieves detailed information about a client by their unique Client ID.
Typical use cases include:
- Fetching client details to enrich transport or logistics workflows.
- Automating client data retrieval for reporting or auditing.
- Integrating client information into other systems or processes within n8n.
For example, you might use this node to get a client's contact info before creating a shipment order or to verify client status during invoicing.
Properties
| Name | Meaning |
|---|---|
| Client ID | The unique numeric identifier of the client whose details you want to retrieve. Required. |
Output
The node outputs JSON data representing the client details fetched from Everest TMS. The structure typically includes fields such as client name, contact information, address, and any other metadata associated with the client in the system.
If multiple clients were retrieved (not typical for a single "Get" operation), the output would be an array of client objects.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node internally calls the Everest API endpoints to fetch client data.
- Proper configuration of the Everest API credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Client ID will cause the API call to fail.
- Authentication errors if the API key credential is not set up correctly.
- Network or API downtime can lead to request failures.
Error messages:
"Client not found": Verify that the Client ID exists in Everest TMS."Authentication failed": Check your API key credential configuration.- Other HTTP errors: Inspect network connectivity and API status.
To resolve errors, ensure the Client ID is correct, credentials are valid, and the Everest TMS service is operational.
Links and References
- Everest TMS official API documentation (refer to your internal or vendor-provided docs)
- n8n documentation on creating custom nodes
- General REST API troubleshooting guides