Everest

Interact with Everest TMS (Transport Management System)

Actions55

Client Actions
General Actions
Mission Actions
Agent Actions
Invoice Actions
Contact Actions
Alert Actions
- Create
- Get Many
Walter Actions
- Send Prompt
- Send Message
Notification Actions
Webhook Actions
- Subscribe
- Unsubscribe
Route Actions
Export Actions
- Create Export

Overview

The node integrates with Everest TMS (Transport Management System) to perform various operations across multiple resources such as General, Mission, Client, Agent, Invoice, Contact, Alert, Walter, Notification, Webhook, Route, and Export. Specifically, the General - Get Services operation fetches a list of services available in the system, optionally filtered by an establishment.

This node is useful for transport management workflows where you need to retrieve service-related data dynamically, for example:

Populating dropdowns with available services in a UI.
Filtering services by specific establishments to manage or assign transport tasks.
Integrating service data into broader logistics automation pipelines.

Properties

Name	Meaning
Options	A collection of optional filters to refine the results:
Search	(Only for "Get Skills" operation) A search term string to filter skills by name.
Establishment	(For "Get Services", "Get Areas Of Service", "Get Availabilities") Select an establishment to filter the results by its ID. The options are dynamically loaded from existing establishments.

Note: For the Get Services operation, only the "Establishment" option applies.

Output

The output is a JSON array where each item represents a service object with at least the following fields:

name: The display name of the service (derived from title or name).
value: The unique identifier of the service.
description: Optional description text about the service.

Example output item:

{
  "name": "Standard Delivery",
  "value": "service_id_123",
  "description": "Delivery service within 24 hours"
}

No binary data output is produced by this operation.

Dependencies

Requires an API key credential for authenticating with the Everest TMS API.
The node uses POST requests to the Everest API endpoints such as /services and /establishments.
Dynamic loading of options (e.g., establishments) depends on successful API calls.
No additional external dependencies beyond the configured Everest API credentials.

Troubleshooting

Empty Results: If no services are returned, verify that the selected establishment ID is correct and that the API user has access rights to view services for that establishment.
API Request Failures: Network issues or invalid API credentials will cause errors. Ensure the API key is valid and the Everest API endpoint is reachable.
Option Loading Errors: If dropdowns like Establishment fail to load options, check API connectivity and permissions.
Continue On Fail Behavior: If enabled, errors during execution will be captured in the output as error messages instead of stopping the workflow.

Links and References

Everest TMS Official Documentation (hypothetical link)
n8n Documentation on Creating Custom Nodes
REST API concepts for POST requests

This summary is based solely on static analysis of the provided source code and property definitions.

EverestInstall