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
The "Export" resource with the "Create Export" operation in this node allows users to generate data exports from the Everest Transport Management System (TMS). Users can export various types of entities such as missions, routes, waybills, statuses, clients, agents, users, invoices, establishments, contacts, and services. The exported data can be filtered, customized by selecting specific fields, and output in multiple formats including CSV, JSON, Excel (XLSX), or ZIP archives.
This node is beneficial for scenarios where users need to extract large datasets for reporting, backup, integration with other systems, or offline analysis. For example, a logistics manager might export mission data filtered by date range and status to analyze delivery performance, or an accounting team might export invoice data for financial reconciliation.
Properties
| Name | Meaning |
|---|---|
| Export Type | Type of entity to export. Options include: Missions, Routes, Waybills, Status, Clients, Agents, Users, Invoices, Establishments, Contacts, Services. |
| Export Format | Format of the export file. Options are CSV, JSON, Excel (XLSX), and ZIP Archive. |
| Fields to Export | List of specific fields to include in the export for the selected Export Type. If empty, all available fields will be exported. Each Export Type has its own set of selectable fields, e.g., for Missions: Reference, Start Date, Client Name, etc. |
| Filters | Collection of filters to narrow down the exported data: - Statuses: Filter by specific statuses. - Services: Filter by specific services. - Agent: Filter by agent. - Client: Filter by client. - Establishment: Filter by establishment. - Date Field: Select which date field to use for filtering (Date Created, Start Date, Status Date Created). - Date From: Start of date/time range filter. - Date To: End of date/time range filter. - Search: Keywords to filter data. |
Output
The node outputs a JSON array containing the exported data records according to the selected type, fields, and filters. The structure of each record corresponds to the fields chosen in the "Fields to Export" property. If no fields are specified, all fields for that entity type are included.
If the export format is a file type (CSV, XLSX, ZIP), the node typically returns the data in binary form suitable for download or further processing within n8n workflows.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node depends on the Everest TMS service being accessible via its API endpoints.
- No additional external dependencies are required beyond the configured API credentials.
Troubleshooting
- Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Selecting incompatible fields or filters may result in empty exports or errors.
- Large data exports might time out or exceed API limits; consider applying filters to reduce dataset size.
- Error Messages:
- Authentication errors indicate invalid or expired API keys; verify and update credentials.
- Validation errors on fields or filters suggest incorrect parameter values; review property selections.
- Network or timeout errors may require retrying or checking network connectivity to the Everest API.
Links and References
- Everest TMS official API documentation (refer to your Everest TMS provider for exact URL)
- n8n documentation on creating custom nodes and handling binary data
- Guides on exporting data in CSV, JSON, XLSX, and ZIP formats for integration purposes