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 → Accept
AI-generatedOverview
The node interacts with the Everest Transport Management System (TMS) to accept a mission. This operation is useful in scenarios where an agent or system needs to programmatically confirm acceptance of a mission, such as in logistics or transport management workflows. For example, an agent can accept a mission assignment directly through this node, updating the mission status in the Everest TMS.
Use Case Examples
- An agent accepts a mission by providing the mission reference and selecting their agent ID.
- Automating mission acceptance in a workflow where missions are assigned and need confirmation before proceeding.
Properties
| Name | Meaning |
|---|---|
| Mission Reference | The reference identifier of the mission to accept, used to specify which mission is being accepted. |
| Agent | The agent who is accepting the mission, selected from a list of available agents loaded dynamically via the getAgents method. |
Output
JSON
missionId- The unique identifier of the accepted mission.status- The status of the mission after acceptance, indicating success or failure.agentId- The identifier of the agent who accepted the mission.message- Additional information or confirmation message about the acceptance operation.
Dependencies
- Requires an API key credential for Everest TMS to authenticate and authorize requests.
Troubleshooting
- If the mission reference is invalid or missing, the node may throw an error indicating the mission cannot be found or accepted.
- If the agent ID is not provided or invalid, the acceptance may fail or be rejected by the API.
- Network or authentication issues with the Everest API can cause request failures; ensure the API key credential is valid and network connectivity is stable.