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 "Mission - Set Status" operation in this node allows users to update the status of one or multiple missions within the Everest Transport Management System (TMS). This is useful for tracking the progress or state changes of transport missions, such as marking a mission as "In Progress," "Completed," or any other custom status defined in the system.
Typical use cases include:
- Automatically updating mission statuses based on external triggers or workflow conditions.
- Adding contextual details like comments, GPS coordinates, or signatures when changing a mission's status.
- Managing multiple missions at once by specifying several mission references in a single operation.
For example, a logistics company could use this node to mark all missions assigned to a driver as "Started" when the driver begins their route, including a GPS location and a signature image for verification.
Properties
| Name | Meaning |
|---|---|
| Mission References | Comma-separated list of mission identifiers to update. Example: ABC123XXX,DEF456YYY,GHI789ZZZ |
| Status | The new status to assign to the specified mission(s). Options are dynamically loaded from the system's available statuses. |
| Status Details | Additional information about the status update, including: |
| - Comment: A textual note explaining the status change. | |
| - Signature (Base64): A base64 encoded image representing a signature related to the status update. | |
| - Latitude: GPS latitude coordinate where the status was updated. | |
| - Longitude: GPS longitude coordinate where the status was updated. |
Output
The node outputs a JSON array containing the results of the status update operations. Each element corresponds to an input item processed and typically includes confirmation data or the updated mission information returned by the Everest API.
If binary data is involved (e.g., signature images), it is expected to be handled as base64 strings within the JSON output rather than separate binary attachments.
Dependencies
- Requires an active connection to the Everest TMS API via an API key credential configured in n8n.
- The node depends on the Everest API endpoints for missions and statuses.
- Dynamic loading of options (like statuses) requires successful API calls to Everest services.
Troubleshooting
- Empty or invalid mission references: Ensure that the "Mission References" field contains valid, comma-separated mission IDs recognized by Everest.
- Invalid status value: The selected status must exist in the Everest system. If no statuses load, verify API connectivity and credentials.
- API errors: Errors returned from the Everest API (e.g., permission denied, mission not found) will appear in the node output if "Continue On Fail" is enabled; otherwise, they will stop execution.
- Malformed base64 signature: The signature string must be properly base64 encoded. Invalid encoding may cause the API to reject the update.
- Missing GPS coordinates: Latitude and longitude should be valid decimal strings if provided; otherwise, omit them.
Links and References
- Everest TMS Official Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- Base64 Encoding Reference