Actions60
- General Actions
- Mission Actions
- Client Actions
- Agent Actions
- Invoice Actions
- Contact Actions
- Alert Actions
- Walter Actions
- Notification Actions
- Webhook Actions
- Route Actions
- Export Actions
Export → Create Export
AI-generatedOverview
This node operation allows users to create data exports from the Everest Transport Management System (TMS). It supports exporting various types of entities such as missions, routes, waybills, statuses, clients, agents, users, invoices, establishments, contacts, and services. Users can specify the export format (CSV, JSON, Excel XLSX, or ZIP archive) and select specific fields to include in the export. Additionally, filters can be applied to narrow down the exported data based on criteria like statuses, services, agents, clients, establishments, date ranges, and search keywords. This operation is useful for generating reports, backups, or data transfers for analysis or integration with other systems.
Use Case Examples
- Exporting mission data in Excel format with selected fields like reference, start date, client name, and status.
- Creating a JSON export of client data filtered by specific statuses and date ranges.
- Generating a ZIP archive containing route data with all available fields for offline analysis.
Properties
| Name | Meaning |
|---|---|
| Export Type | Type of entity to export, such as missions, routes, waybills, statuses, clients, agents, users, invoices, establishments, contacts, or services. |
| Export Format | Format of the export file, such as CSV, JSON, Excel (XLSX), or ZIP archive. |
| Fields to Export | List of fields to include in the export. If empty, all fields will be exported. The available fields depend on the selected export type (e.g., missions, routes, waybills, etc.). |
| Filters | Optional filters to apply to the export data, including statuses, services, agent, client, establishment, date field for filtering, date range, and search keywords. |
Output
JSON
exportData- The exported data in the selected format containing the requested fields and filtered according to the specified criteria.
Dependencies
- Everest TMS API with appropriate API key credentials
Troubleshooting
- Ensure the API credentials are correctly configured and have sufficient permissions to access the requested data.
- Verify that the selected export type and fields are valid and supported by the Everest TMS API.
- Check date filters and other filter criteria for correctness to avoid empty or incomplete exports.
- If the export operation fails, review error messages for details and adjust parameters accordingly.
Links
- Everest TMS API Documentation - Official API documentation for Everest Transport Management System, useful for understanding export capabilities and parameters.