Overview

This node operation creates a new mission in the Everest Transport Management System (TMS). It is useful for logistics and transport companies to schedule and manage transport missions by specifying details such as service, start and end addresses, client, agent, shipment details, and custom information. For example, a user can create a mission to transport goods from one location to another, assign an agent, and include package details and special instructions.

Use Case Examples

1. Create a mission with a specified service, start and end addresses, and assign an agent for delivery.
2. Create a mission including detailed package information such as weight, volume, and dimensions.
3. Create a mission with custom fields and comments for internal tracking and client references.

Properties

Output

JSON

• id - Unique identifier of the created mission.
• service_id - Identifier of the service assigned to the mission.
• address_start - Starting address of the mission.
• address_end - Destination address of the mission.
• start_date - Scheduled start date and time of the mission.
• client_id - Identifier of the client who created the mission.
• agent_id - Identifier of the agent assigned to the mission.
• client_ref - Client's internal reference for the mission.
• comment - Additional comments related to the mission.
• weight - Weight of the shipment in kilograms.
• volume - Volume of the shipment in cubic meters.
• price_excl - Price of the mission excluding taxes.
• agent_price_excl - Price paid to the agent excluding taxes.
• status - Current status of the mission.
• check_date - Flag indicating if the scheduled date was validated.
• check_addresses - Flag indicating if the addresses were validated.
• establishment_id - Identifier of the establishment related to the 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 - Array of custom information fields with name and value pairs.
• packages - Array of package details including name, weight, volume, dimensions, reference, quantity, and scannable flag.

Dependencies

• Everest TMS API
• An API key credential for Everest TMS

Troubleshooting

• Ensure all required fields are correctly filled, especially addresses and service selection if applicable.
• If the API request fails, check the API key credential and network connectivity.
• Validation flags (check_date, check_addresses) may cause errors if dates or addresses are invalid; verify input data format and correctness.
• Error messages from the API typically indicate missing or invalid parameters; review the mission details and correct any issues.

Links

• Everest TMS API Documentation - Official API documentation for Everest Transport Management System.