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
Mission → Mark as Seen
AI-generatedOverview
This node interacts with the Everest Transport Management System (TMS) to mark a specific mission as seen. It is useful in scenarios where users need to update the status of missions to indicate they have been acknowledged or reviewed, helping in workflow tracking and management within the Everest TMS.
Use Case Examples
- A logistics manager marks a delivery mission as seen after reviewing its details.
- An agent updates the mission status to seen to notify the system that the mission has been acknowledged.
Properties
| Name | Meaning |
|---|---|
| Mission Reference | The reference identifier of the mission to mark as seen. This property is optional and used to specify which mission to update. |
Output
JSON
id- The unique identifier of the mission that was marked as seen.status- The updated status of the mission after being marked as seen.message- A confirmation message indicating the mission has been successfully marked as seen.
Dependencies
- Requires an API key credential for Everest TMS to authenticate requests.
Troubleshooting
- If the mission reference is incorrect or missing, the node may fail to find the mission to update. Verify the mission reference value.
- API authentication errors may occur if the Everest API key credential is invalid or expired. Ensure valid credentials are configured.
- Network or server errors from the Everest TMS API can cause operation failures. Check network connectivity and Everest service status.