Everest icon

Everest

Interact with Everest TMS (Transport Management System)

Overview

This node integrates with the Everest Transport Management System (TMS) to perform various operations on different resources. Specifically, for the Invoice - Get operation, it retrieves detailed information about a single invoice by its ID. This is useful in scenarios where you need to fetch invoice data for review, reporting, or further processing within an automated workflow.

Practical examples:

  • Automatically retrieving invoice details after a shipment is completed to update accounting systems.
  • Fetching invoice data to generate custom reports or dashboards.
  • Using invoice information to trigger notifications or alerts based on payment status.

Properties

Name Meaning
Invoice ID The ID of the invoice to retrieve. It must be a number and is required for this operation.

Output

The node outputs JSON data representing the invoice details fetched from Everest TMS. The structure typically includes all relevant invoice fields such as invoice number, date, client information, amounts, status, and line items.

If the node supports binary data output (not indicated here), it would typically represent attachments like PDF copies of invoices, but this is not evident from the provided code.

Dependencies

  • Requires an API key credential for authenticating requests to the Everest TMS API.
  • The node internally calls a helper function to make authenticated POST requests to Everest endpoints.
  • No additional external dependencies are indicated beyond the Everest API access.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Invoice ID will likely result in an error or empty response.
    • Network or authentication failures if the API key is missing, expired, or incorrect.
    • Rate limiting or API quota exceeded errors from Everest TMS.
  • Error messages:

    • Errors thrown during execution will include the message from the Everest API or network layer.
    • If "Continue On Fail" is enabled, errors will be returned as part of the output JSON with an error field containing the message.
  • Resolutions:

    • Verify that the Invoice ID is correct and exists in the Everest system.
    • Ensure the API key credential is properly configured and has necessary permissions.
    • Check network connectivity and Everest API status.
    • Enable "Continue On Fail" to handle errors gracefully in workflows.

Links and References

Discussion