Everest icon

Everest

Interact with Everest TMS (Transport Management System)

Actions60

Mission → Update

AI-generated

Overview

This node updates an existing mission in the Everest Transport Management System (TMS). It allows users to modify various details of a mission such as the mission reference, service, start and end addresses, scheduling, client and agent assignments, shipment details, pricing, status, and custom information. This node is useful for logistics and transport management scenarios where mission details need to be adjusted after creation, for example, changing the delivery address, updating the assigned agent, or modifying shipment weight and volume.

Use Case Examples

  1. Updating the destination address and scheduled start date of a delivery mission.
  2. Changing the assigned agent and updating the mission status to 'In Progress'.
  3. Adding custom information fields and package details to an existing mission.

Properties

Name Meaning
Mission Reference The reference identifier of the mission to update.
Service The service associated with the mission; optional and can be left empty to keep the current service.
Start Address The starting address for the mission.
End Address The destination address for the mission.
Additional Fields A collection of optional fields to provide more details about the mission such as start date, client, agent, client reference, comments, shipment weight and volume, pricing, status, validation flags, and establishment.
Start Address Details Details about the start address including contact name, company, email, phone, and special instructions.
End Address Details Details about the end address including contact name, company, email, phone, and special instructions.
Custom Information Custom fields with name and value pairs to add additional information to the mission.
Packages Details about packages included in the mission such as name, weight, volume, dimensions, reference number, quantity, and whether the package is scannable.

Output

JSON

  • id - Unique identifier of the updated mission.
  • ref - Reference of the updated mission.
  • service_id - Service associated with the updated mission.
  • address_start - Starting address of the updated mission.
  • address_end - Destination address of the updated mission.
  • start_date - Scheduled start date and time of the updated mission.
  • client_id - Client who created the updated mission.
  • agent_id - Agent assigned to the updated mission.
  • client_ref - Client's internal reference for the updated mission.
  • comment - Additional comments for the updated mission.
  • weight - Weight of the shipment in kilograms for the updated mission.
  • volume - Volume of the shipment in cubic meters for the updated mission.
  • price_excl - Price of the mission excluding taxes.
  • agent_price_excl - Price paid to the agent excluding taxes.
  • status - Status of the updated mission.
  • establishment_id - Establishment associated with the updated mission.
  • address_start_name - Contact name at the start address.
  • address_start_company - Company name at the start address.
  • address_start_email - Email of the contact at the start address.
  • address_start_tel - Phone number of the contact at the start address.
  • address_start_comment - Special instructions for the start address.
  • address_end_name - Contact name at the end address.
  • address_end_company - Company name at the end address.
  • address_end_email - Email of the contact at the end address.
  • address_end_tel - Phone number of the contact at the end address.
  • address_end_comment - Special instructions for the end address.
  • custom_infos - Custom information fields added to the mission.
  • packages - Details of packages included in the mission.

Dependencies

  • An API key credential for Everest TMS

Troubleshooting

  • Ensure the mission reference (ref) is correct and corresponds to an existing mission to update.
  • Verify that the service_id and other option fields are valid and exist in the Everest system.
  • Check that the addresses are properly formatted if address validation is enabled.
  • If the node throws errors related to permissions, verify that the API key credential has sufficient rights to update missions.
  • Network or API downtime can cause request failures; retry or check Everest TMS status if issues persist.

Links

Discussion