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) API, allowing users to perform various operations on different resources within Everest. Specifically, for the Agent resource with the Get operation, it retrieves detailed information about a single agent by their unique ID.
Typical use cases include:
- Fetching agent details to display or process in workflows.
- Integrating agent data into other systems or reports.
- Automating updates or notifications based on agent information.
For example, you might use this node to get an agent's contact details before assigning them to a mission or to verify agent status during workflow execution.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique numeric identifier of the agent to retrieve. This is a required field. |
Output
The node outputs a JSON array where each item corresponds to the retrieved agent data object. The structure of the json output typically includes all available fields returned by the Everest API for an agent, such as:
- Agent personal details (e.g., first name, last name, email)
- Contact information
- Status and skills
- Any other metadata associated with the agent in Everest TMS
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Everest TMS API.
- Needs an API key credential configured in n8n for authentication.
- The node uses POST requests internally to interact with the Everest API endpoints.
Troubleshooting
Common issues:
- Invalid or missing Agent ID will cause the API call to fail.
- Network or authentication errors if the API key is incorrect or expired.
- If the specified agent does not exist, the API may return an error or empty response.
Error messages:
"Agent not found"or similar indicates the provided Agent ID does not correspond to any existing agent.- Authentication errors suggest checking the API key credential setup.
- Timeout or network errors require verifying connectivity to the Everest API endpoint.
To resolve these, ensure the Agent ID is correct, the API credentials are valid, and the Everest service is reachable.
Links and References
- Everest TMS API Documentation (example placeholder, replace with actual URL if known)
- n8n documentation on creating custom nodes