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 retrieve various types of data related to transport services, missions, clients, agents, invoices, contacts, alerts, notifications, webhooks, routes, and exports. Specifically, for the General resource with the Get Areas of Service operation, it fetches areas of service data filtered optionally by establishment or search terms.
Typical use cases include:
- Fetching a list of areas of service available in the system to display or process further.
- Filtering areas of service by a specific establishment to narrow down results.
- Using the retrieved data to automate workflows involving transport service planning or reporting.
Example: A logistics company could use this node to get all areas of service linked to a particular warehouse (establishment) to plan delivery routes accordingly.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of optional filters to refine the query: |
| Search | A search term string to filter results by keyword (only applicable for "getSkills" operation, not for "getAreasOfService"). |
| Establishment | Select an establishment to filter areas of service associated with that establishment. The options are dynamically loaded from existing establishments in the system. |
Note: For the Get Areas of Service operation, only the Establishment option is relevant.
Output
The node outputs a JSON array where each item represents an area of service object retrieved from Everest TMS. Each object typically contains fields such as:
id: Unique identifier of the area of service.nameortitle: The name/title of the area of service.- Other descriptive fields depending on the API response.
The exact structure depends on the Everest API response but generally includes identifiers and descriptive metadata about each area of service.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Everest TMS API.
- Needs an API authentication credential configured in n8n (referred generically as an API key credential).
- The node uses internal methods to load dynamic options such as establishments, which depend on successful API calls.
Troubleshooting
- Empty Results: If no areas of service are returned, verify that the selected establishment ID is correct and that the user’s API credentials have sufficient permissions.
- API Request Failures: Network issues or invalid credentials can cause request failures. Ensure the API key credential is valid and the Everest API endpoint is reachable.
- Option Loading Errors: Dynamic loading of establishments may fail if the API is unreachable or returns unexpected data. Check connectivity and API status.
- Error Messages: Errors thrown by the node will usually contain messages from the Everest API. Common errors include authentication failures, invalid parameters, or rate limiting. Review the error message and adjust credentials or input parameters accordingly.
If the node is set to continue on failure, errors will be included in the output JSON under an error field.
Links and References
- Everest TMS Official Documentation (example placeholder, replace with actual URL if known)
- n8n Documentation on Creating Custom Nodes
- Everest API Reference (if publicly available)
This summary is based solely on static analysis of the provided source code and property definitions.