EverestInstall

Overview

This node integrates with the Everest Transport Management System (TMS) to perform various operations across multiple resources such as missions, clients, agents, invoices, contacts, alerts, notifications, webhooks, routes, exports, and general queries.

Specifically, for the General resource with the Check Address operation, the node allows users to verify or validate an address within the Everest system. This can be useful in logistics workflows where confirming the accuracy or serviceability of an address is critical before scheduling transport missions or deliveries.

Practical examples:

• Validating a customer’s delivery address before creating a shipment.
• Checking if a given address falls within the service area of a specific transport service.
• Scheduling missions only for addresses confirmed as valid by the system.

Properties

Output

The node outputs a JSON array containing the results of the address check operation. Each item in the output corresponds to the response from the Everest API regarding the validity or details of the checked address.

The exact structure depends on the Everest API response but typically includes fields indicating whether the address is valid, any normalized address data, and possibly related service availability information.

No binary data output is indicated for this operation.

Dependencies

• Requires an API key credential for authenticating with the Everest TMS API.
• The node uses internal methods to load dynamic options such as available services.
• Network access to the Everest API endpoints is necessary.
• No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials will cause authentication failures.
  • Providing an improperly formatted address may result in errors or invalid responses.
  • Selecting a service that does not exist or is unavailable could lead to empty or error responses.

• Error messages:

  • Errors returned from the Everest API will be propagated; typical messages might include "Invalid address format" or "Service not found".
  • If the node is set to continue on fail, errors will appear in the output JSON under an error field.

• Resolutions:

  • Ensure the API key credential is correctly configured and has sufficient permissions.
  • Validate the address format before input.
  • Use the node’s dynamic dropdowns to select valid services.

Links and References

• Everest TMS official documentation (not provided here, but typically available from the service provider).
• n8n documentation on creating custom nodes.
• General REST API best practices for address validation services.