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 perform various operations on different resources. Specifically, for the Invoice resource with the Get Many operation, it retrieves multiple invoices from the system based on optional filtering and pagination parameters.
Typical use cases include:
- Fetching a list of invoices for reporting or auditing purposes.
- Retrieving invoices matching certain search criteria to display in dashboards.
- Paginating through large sets of invoices to process them in batches.
For example, you might use this node to get the first 50 invoices containing a specific keyword in their description or to fetch invoices starting from a particular offset for batch processing.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of optional parameters to control the query: |
| - Limit | Maximum number of invoices to return (default 50). |
| - Limit Start | Starting offset for pagination, zero-based index (default 0). |
| - Search | Search term to filter invoices by matching text fields (e.g., invoice number, client). |
Output
The node outputs an array of JSON objects representing invoices retrieved from Everest TMS. Each object corresponds to one invoice and contains its details as provided by the API.
The exact structure of each invoice object depends on the Everest API response but typically includes fields such as invoice ID, client information, amounts, dates, status, and other relevant metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Everest TMS API via an API key credential configured in n8n.
- The node internally calls the Everest API endpoints to fetch invoice data.
- Proper network access and valid credentials are necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Network connectivity problems can prevent API requests from succeeding.
- Using a
limitvalue too high may result in timeouts or performance degradation. - Providing invalid search terms or offsets may yield empty results.
Error messages:
- Authentication errors usually indicate incorrect or expired API keys; verify and update credentials.
- Timeout or connection errors suggest network issues; check firewall and internet access.
- API response errors may occur if the requested parameters are invalid; review input values.
Links and References
- Everest TMS official API documentation (refer to your provider's docs for detailed API specs).
- n8n documentation on creating and using API key credentials.
- General REST API pagination and filtering best practices.