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) to perform various operations on different resources such as contacts, missions, clients, agents, invoices, and more. Specifically, the Contact - Get operation retrieves detailed information about a single contact by its unique ID.
Typical use cases include:
- Fetching contact details for display or further processing in workflows.
- Integrating contact data from Everest TMS into other systems or databases.
- Automating updates or notifications based on contact information.
For example, you might use this node to get the full profile of a contact before sending them a notification or updating their status in another system.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique numeric identifier of the contact to retrieve. This is required to specify which contact's data should be fetched. |
Output
The node outputs an array of JSON objects representing the contact data retrieved from Everest TMS. Each object contains the fields and values corresponding to the contact's details as stored in the system.
- The
jsonoutput field includes all available properties of the contact, such as name, email, phone number, address, and any custom fields defined in Everest. - The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the Everest TMS API.
- The node depends on the Everest TMS service being accessible and the provided Contact ID existing in the system.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Contact ID will likely result in an error or empty response.
- Network connectivity problems or incorrect API credentials can cause authentication failures.
- If the Everest TMS API changes or is temporarily unavailable, requests may fail.
Error messages:
- Errors related to "contact not found" indicate the specified Contact ID does not exist; verify the ID.
- Authentication errors suggest invalid or missing API credentials; check the configured API key.
- Timeout or network errors require checking internet connection and Everest TMS service status.
Links and References
- Everest TMS official API documentation (refer to your internal or vendor-provided docs).
- n8n documentation on creating and using API credentials.
- General REST API best practices for troubleshooting connectivity and authentication issues.