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 allows updating an existing mission in the Everest Transport Management System (TMS). It is useful for logistics, transportation, or delivery companies that need to modify details of a scheduled mission such as addresses, assigned agents, client information, shipment details, and status. For example, if a delivery address changes after a mission has been created, this node can update the mission with the new address and related contact details.
Typical use cases include:
- Changing the start or end address of a mission.
- Assigning or reassigning an agent to a mission.
- Updating shipment weight, volume, or pricing information.
- Adding comments or custom fields to provide additional context.
- Modifying the scheduled start date or status of the mission.
Properties
| Name | Meaning |
|---|---|
| Mission Reference | The unique reference identifier of the mission to update. |
| Service | The service associated with the mission. Optional; leave empty to keep the current service. Options are dynamically loaded from available services. |
| Start Address | The starting address for the mission (e.g., "42 fake street, 75001 Paris"). |
| End Address | The destination address for the mission. |
| Additional Fields | A collection of optional fields including: - Service (alternative way to specify service) - Start Date (scheduled start datetime) - Client (client who created the mission) - Agent (assigned agent) - Client Reference (internal client ref) - Comment (additional notes) - Weight (kg) - Volume (m³) - Price Excluding Tax - Agent Price Excluding Tax - Status (mission status) - Check Date (boolean to validate scheduled date) - Check Addresses (boolean to validate addresses) - Establishment (associated establishment) |
| Start Address Details | Contact details for the start address including: - Contact Name - Company - Phone - Comment (special instructions) |
| End Address Details | Contact details for the end address including: - Contact Name - Company - Phone - Comment (special instructions) |
| Custom Information | Multiple custom key-value pairs to add extra information to the mission. Each entry includes a name and a value. |
| Packages | Multiple packages associated with the mission. Each package can have: - Name - Weight (kg) - Volume (m³) - Length (cm) - Width (cm) - Depth (cm) - Reference number - Quantity - Is Scannable (boolean indicating if package has a scannable code) |
Output
The node outputs a JSON array where each element corresponds to the updated mission data returned by the Everest TMS API. The structure typically contains all updated mission fields reflecting the changes made, such as updated addresses, assigned agents, shipment details, and status.
If the node supports binary data output (not indicated here), it would represent files or attachments related to the mission, but this node primarily deals with JSON data representing mission records.
Dependencies
- Requires an active connection to the Everest TMS API using an API key credential configured in n8n.
- Dynamic options for properties like Service, Client, Agent, Status, and Establishment are loaded via API calls to Everest endpoints.
- Proper permissions on the Everest account to update missions.
Troubleshooting
Common issues:
- Providing an invalid or non-existent mission reference will cause the update to fail.
- Omitting required authentication or having expired credentials will result in authorization errors.
- Invalid address formats or missing mandatory fields may cause validation errors from the API.
- Network connectivity issues can prevent communication with the Everest API.
Error messages:
"Mission not found": Verify the mission reference is correct."Unauthorized"or"Invalid API key": Check the API key credential configuration."Validation error": Review the input fields for correctness, especially addresses and dates."Failed to load options": Indicates problems fetching dynamic dropdown values; check API availability.
To resolve errors, ensure all required fields are correctly set, credentials are valid, and the mission reference exists in the system.
Links and References
- Everest TMS official API documentation (refer to your Everest provider's docs)
- n8n documentation on creating and configuring API credentials
- General REST API usage best practices