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 update client information. It allows users to modify various details of an existing client record, such as contact info, billing data, status, and custom fields. This is useful in scenarios where client data changes over time—like updating addresses, contact emails, or billing preferences—and you want to keep your TMS client records current without manual intervention.
Practical examples include:
- Updating a client's email and phone number after they notify you of changes.
- Changing the VAT rate or accounting codes for a client due to regulatory updates.
- Adding or modifying custom information fields required for specific missions or contracts.
Properties
| Name | Meaning |
|---|---|
| Client ID | The unique numeric identifier of the client to update (required). |
| Additional Fields | Optional extra client details that can be updated, including: |
| - Internal Code: Internal reference code for the client. | |
| - Accounting Code: Accounting reference code. | |
| - VAT Rate (%): VAT percentage applied to the client. | |
| - VAT Number: VAT identification number. | |
| - Address Line 1 & 2: Primary and secondary address lines. | |
| - Billing Name, Email, Address, Complementary Info: Billing-related information. | |
| - Fuel Surcharge: Percentage surcharge applied to missions. | |
| - Photo (Base64): Base64 encoded profile photo of the client. | |
| - Periodic Invoicing: Whether the client is invoiced periodically (boolean). | |
| - Invoice Period: Options like "1st of Month" for periodic invoicing. | |
| - Invoice Period Extra: Additional parameter for invoicing period. | |
| - Status: Client account status, either Active or Inactive. | |
| - Establishment: The establishment this client belongs to (loaded dynamically). | |
| Update Fields | Core client personal information fields to update, including: |
| - Email, First Name, Last Name, Phone. | |
| - Password and Confirm Password: For changing the client's password securely. | |
| Custom Information Requirements | Multiple custom info fields with name and mandatory flag, used for mission creation requirements. |
Output
The node outputs a JSON array containing the updated client data returned from the Everest API. Each item corresponds to one input item processed and includes the updated client properties as confirmed by the system.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Everest TMS API via an API key credential configured in n8n.
- The node uses internal helper functions to make authenticated POST requests to the Everest API endpoints.
- Dynamic dropdown options (e.g., establishments) are loaded via API calls within the node.
Troubleshooting
Common Issues:
- Invalid or missing Client ID will cause the update to fail.
- Mismatched passwords in "Password" and "Confirm Password" fields may result in errors.
- Providing invalid values for enumerated fields like Status or Invoice Period can cause API rejections.
- Network or authentication failures with the Everest API will prevent updates.
Error Messages:
"Client not found": Verify the Client ID exists in the system."Password confirmation does not match": Ensure both password fields are identical."Invalid field value": Check that all fields conform to expected formats and allowed values.- Authentication errors: Confirm API credentials are correctly set up in n8n.
Links and References
- Everest TMS official API documentation (not provided here; consult your Everest TMS provider).
- n8n documentation on creating and using API credentials.
- General best practices for managing client data in transport management systems.