Everest icon

Everest

Interact with Everest TMS (Transport Management System)
Join our community

Actions55

Overview

The node integrates with the Everest Transport Management System (TMS) to update agent information. It allows users to modify various details of an existing agent, such as contact info, availability, pricing preferences, location coordinates, and account status.

This node is beneficial in scenarios where agent data needs to be kept current within the TMS platform, for example:

  • Updating an agent’s contact details or address after relocation.
  • Changing an agent’s availability status or pricing limits based on new agreements.
  • Modifying login credentials like password for security updates.
  • Associating an agent with a different establishment.

Practical example: A logistics company automates updating their drivers’ profiles in Everest TMS whenever HR changes occur, ensuring dispatchers always have accurate agent data.

Properties

Name Meaning
Agent ID The unique identifier of the agent to update.
Additional Fields Optional fields to update additional agent details:
- Phone number
- Secondary address line
- Billing name and address
- Company number
- Minimum and maximum price accepted for missions
- Maximum travel distance in km
- GPS latitude and longitude
- Base64 encoded profile photo
- Availability status (boolean)
- Account status (Active or Inactive)
- Establishment the agent belongs to
Update Fields Core fields to update agent's personal and login information:
- Email address
- First name
- Last name
- New password
- Confirm new password

Output

The node outputs a JSON array containing the updated agent data returned from the Everest TMS API. Each item corresponds to one input item processed and includes the updated properties of the agent.

If the operation fails for any item and "Continue On Fail" is enabled, the output will include an error object with the error message for that item.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the Everest TMS API.
  • The node depends on the Everest TMS service being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Invalid or missing Agent ID will cause the update to fail.
    • Providing mismatched passwords in "Password" and "Confirm Password" fields may result in errors.
    • Network or authentication failures with the Everest API can prevent successful updates.
    • Attempting to update fields with invalid formats (e.g., non-numeric values for numeric fields) may cause errors.

  • Error messages:

    • "Agent not found": Verify the Agent ID exists in the system.
    • "Authentication failed": Check that the API key credential is valid and has necessary permissions.
    • "Password confirmation does not match": Ensure both password fields match exactly.
    • "Invalid field value": Review the input values for correctness and type compliance.

Resolving these typically involves verifying input parameters, checking credentials, and ensuring network connectivity.

Links and References

Discussion