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 integrates with the Everest Transport Management System (TMS) to create new missions. A mission typically represents a transport or delivery task, including details such as start and end addresses, assigned agents, clients, packages, and scheduling information.
Common scenarios for using this node include automating the creation of transport orders from other systems, managing logistics workflows, or integrating shipment requests into Everest TMS. For example, a logistics company could use this node to automatically create delivery missions when new orders are received in their e-commerce platform.
Properties
| Name | Meaning |
|---|---|
| Service | Select the service associated with the mission. Options are dynamically loaded from available services in Everest TMS. |
| 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 to provide more details about the mission: - Service (alternative way to specify service) - Start Date (scheduled start date/time) - Client (client who created the mission) - Agent (assigned agent) - Client Reference (internal client reference) - Comment (additional comments) - 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, email, phone, and special instructions. |
| End Address Details | Contact details for the end address, similar to start address details. |
| Custom Information | Multiple custom fields can be added, each with a name and value, allowing flexible additional data to be attached to the mission. |
| Packages | One or more packages can be specified, each with properties like name, weight, volume, dimensions (length, width, depth), reference number, quantity, and whether it has a scannable code. |
Output
The node outputs an array of JSON objects representing the created mission(s). Each object contains the details returned by the Everest TMS API after mission creation, which typically includes identifiers, status, timestamps, and all submitted mission data.
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.
Dependencies
- Requires an active connection to the Everest TMS API via an API key credential configured in n8n.
- Uses multiple dynamic option loading methods to fetch lists of services, clients, agents, statuses, and establishments from Everest TMS.
- No other external dependencies are indicated.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing incomplete or invalid addresses may result in validation errors if "Check Addresses" is enabled.
- Scheduling dates must be valid ISO date-time strings; otherwise, validation may fail if "Check Date" is enabled.
- Selecting non-existent services, clients, agents, or establishments will cause errors due to invalid references.
Error Messages:
- Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Validation errors on addresses or dates: Ensure addresses are complete and dates are properly formatted.
- Option loading failures: Network issues or API downtime may prevent loading options; retry later or check connectivity.
Links and References
- Everest TMS Official Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for integration nodes