Everest icon

Everest

Interact with Everest TMS (Transport Management System)

Overview

The node integrates with Everest TMS (Transport Management System) to manage various resources including agents. Specifically, the Agent - Create operation allows users to create a new agent profile within the Everest system. This is useful for transport or logistics companies that need to programmatically add agents who will be assigned missions or tasks.

Typical use cases include:

  • Automating onboarding of new agents by creating their profiles from external HR or CRM systems.
  • Bulk creation of agents during initial setup or migration.
  • Integrating agent creation into workflows that trigger when new personnel join the company.

For example, a workflow could take data from a form submission and automatically create an agent in Everest with their contact details, address, and availability status.

Properties

Name Meaning
Email Email address of the agent (required).
First Name Agent's first name (required).
Last Name Agent's last name (required).
Address Line 1 Primary address line of the agent (required).
Password Password for the agent account (required).
Confirm Password Confirmation of the password (required).
Additional Fields Optional extra fields to provide more details about the agent:
- Phone Phone number of the agent.
- Address Line 2 Secondary address line.
- Billing Name Company name used for billing purposes.
- Billing Address Billing address.
- Company Number Company registration number.
- Minimum Price Minimum price the agent accepts for missions (number).
- Maximum Price Maximum price the agent accepts for missions (number).
- Maximum Distance (km) Maximum distance the agent is willing to travel (number).
- Latitude GPS latitude coordinate of the agent.
- Longitude GPS longitude coordinate of the agent.
- Photo (Base64) Base64 encoded string representing the agent’s profile photo.
- Available Boolean indicating if the agent is currently available for missions.
- Status Account status of the agent; options are Active (1) or Inactive (0).
- Establishment The establishment (location or branch) the agent belongs to, selectable from loaded options.

Output

The node outputs a JSON array where each element corresponds to the result of creating an agent. The structure typically includes the newly created agent's details as returned by the Everest API, such as their ID, email, name, status, and other relevant metadata.

If the node supports binary data output (not indicated here), it would represent files or images related to the agent, but in this case, only JSON data is expected.

Dependencies

  • Requires an active connection to the Everest TMS API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The node uses internal methods to load dynamic options such as establishments, ensuring up-to-date selections.
  • No additional external dependencies beyond the Everest API and proper credential configuration.

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: Omitting any required field like email, first name, last name, or address line 1 will cause errors.
  • Invalid email format: Providing an improperly formatted email can lead to validation errors.
  • API authentication errors: Ensure the API key or token is valid and has sufficient permissions.
  • Network issues: Connectivity problems with the Everest API endpoint will cause failures.
  • Option loading failures: If dynamic options like establishments fail to load, check API access and network connectivity.

Common error messages usually indicate which required field is missing or invalid, or if authentication failed. Reviewing the error message and verifying input values and credentials typically resolves these issues.

Links and References

Discussion