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 interacts with the Everest Transport Management System (TMS) to retrieve multiple mission records based on various filtering and sorting criteria. The "Get Many" operation under the "Mission" resource allows users to fetch a list of missions, which can be filtered by client, agent, service, status, date ranges, and other parameters. This is useful for scenarios such as generating reports on ongoing or past missions, monitoring active transport tasks, or integrating mission data into other workflows.
Practical examples include:
- Fetching all ongoing missions assigned to a specific agent.
- Retrieving missions started within a certain date range for performance analysis.
- Listing missions filtered by client or service type for customer management.
Properties
| Name | Meaning |
|---|---|
| Limit | Max number of mission results to return. |
| Limit Start | Starting offset for pagination (0-based index). |
| Client | Filter missions by a specific client (selectable from loaded clients). |
| Agent | Filter missions by a specific agent (selectable from loaded agents). |
| Service | Filter missions by a specific service (selectable from loaded services). |
| Search | Search term to filter missions by text matching. |
| Hide Finished Missions | Boolean flag to hide finished missions and only return ongoing ones. |
| Statuses | Filter by specific mission statuses; comma-separated list of status slugs (e.g., delivery-ok,pickup). |
| Start Date From | Filter missions with start date from this date/time (Europe/Paris timezone). |
| Start Date To | Filter missions with start date until this date/time (Europe/Paris timezone). |
| Order By | Field to order results by: Date Created, Date Modified, Last Status Date, Start Date, Distance, Duration. |
| Order Direction | Order direction: Ascending or Descending. |
Output
The node outputs an array of JSON objects representing missions that match the specified filters. Each mission object contains detailed information about the mission, such as identifiers, dates, statuses, associated client, agent, service details, and other relevant metadata.
If binary data were involved (not indicated here), it would typically represent attachments or files related to missions, but this operation focuses on JSON data output.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node uses internal methods to load options dynamically for clients, agents, and services by making authenticated POST requests to the Everest API endpoints.
- No additional external dependencies beyond the configured Everest TMS API access.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Using invalid filter values (e.g., non-existent client or agent IDs) may result in empty results or errors.
- Date filters must respect the Europe/Paris timezone format; incorrect formatting might lead to unexpected filtering behavior.
Error Messages:
- Authentication errors: Verify that the API key credential is correctly set up in n8n.
- Network or API request failures: Check network connectivity and Everest API availability.
- Invalid parameter errors: Ensure that filter inputs conform to expected types and formats.
Links and References
- Everest TMS official API documentation (refer to your organization's internal resources or Everest support).
- n8n documentation on creating and using custom nodes and credentials.