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 manage client data. Specifically, the Client - Create operation allows users to add new clients into the Everest system by providing essential contact and billing information.
Typical use cases include:
- Automating client onboarding workflows by creating client records directly from form submissions or CRM systems.
- Synchronizing client databases between Everest TMS and other platforms.
- Setting up client accounts with detailed billing and contact info for transport management and invoicing.
For example, a logistics company could use this node to automatically create client profiles when new customers sign up on their website, including their contact details, billing preferences, and custom information fields.
Properties
| Name | Meaning |
|---|---|
| Email address of the client | |
| First Name | First name of the client |
| Last Name | Last name of the client |
| Phone | Phone number of the client |
| Password | Password for the client account |
| Confirm Password | Confirmation of the password |
| Additional Fields | Optional extra client details: |
| - Internal Code | Internal reference code for the client |
| - Accounting Code | Accounting reference code |
| - VAT Rate (%) | VAT rate applied to this client (default 20%) |
| - VAT Number | VAT identification number |
| - Address Line 1 | Primary address line |
| - Address Line 2 | Secondary address line |
| - Billing Name | Company name used for billing |
| - Billing Email | Email address used for billing |
| - Billing Address | Billing address |
| - Billing Complementary Info | Additional billing information |
| - Fuel Surcharge | Fuel surcharge percentage applied to missions |
| - Photo (Base64) | Base64 encoded profile photo |
| - Periodic Invoicing | Whether the client is invoiced periodically (boolean) |
| - Invoice Period | Invoicing period for periodic invoicing (e.g., "1st of Month") |
| - Invoice Period Extra | Additional parameter for invoicing period |
| - Status | Client account status ("Active" or "Inactive") |
| - Establishment | The establishment this client belongs to (select from loaded options) |
| Custom Information Requirements | Multiple custom info fields can be added, each with a name and whether it is mandatory for missions |
Output
The node outputs an array of JSON objects representing the created client(s). Each object contains the response data returned by the Everest API after successfully creating a client record. This typically includes client identifiers, confirmation of stored fields, and any metadata returned by the service.
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 Everest endpoints.
- Some input options (like establishments) are dynamically loaded from Everest via API calls.
Troubleshooting
- Password mismatch: If the "Password" and "Confirm Password" fields do not match, the API may reject the request. Ensure both fields are identical.
- Missing required fields: All required fields (email, first name, last name, phone, password, confirm password) must be provided; otherwise, the operation will fail.
- Invalid email format: Providing an improperly formatted email may cause validation errors.
- API authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Network issues: Connectivity problems with the Everest API endpoint will cause failures.
- Dynamic option loading failures: If establishments or other dynamic options fail to load, verify API access and network connectivity.
Links and References
- Everest TMS Official Documentation (example placeholder link)
- n8n Documentation on Creating Custom Nodes
- REST API Best Practices