Everest icon

Everest

Interact with Everest TMS (Transport Management System)

Contact → Update

AI-generated

Overview

This node updates an existing contact in the Everest TMS (Transport Management System). It allows users to specify the contact by its ID and update various fields such as email, phone number, first name, last name, company, job title, and CRM points. This operation is useful for maintaining up-to-date contact information within the system, for example, when a contact's details change or need correction.

Use Case Examples

  1. Updating a contact's email and phone number after they have changed.
  2. Modifying the job title and company information for a contact to reflect their current employment.
  3. Adjusting CRM points for a contact based on recent interactions or achievements.

Properties

Name Meaning
Contact ID The ID of the contact to update, used to identify which contact record to modify.
Update Fields A collection of fields that can be updated for the contact, including email, phone, first name, last name, company, job, and points.

Output

JSON

  • id - The unique identifier of the updated contact.
  • email - The updated email address of the contact.
  • tel - The updated phone number of the contact.
  • first_name - The updated first name of the contact.
  • last_name - The updated last name of the contact.
  • company - The updated company name of the contact.
  • job - The updated job title of the contact.
  • points - The updated CRM points for the contact.

Dependencies

  • An API key credential for Everest TMS is required to authenticate requests.

Troubleshooting

  • If the contact ID is invalid or does not exist, the node will throw an error indicating the contact could not be found. Verify the ID before running the node.
  • Ensure that at least one field is provided in the Update Fields collection; otherwise, the update operation may fail or have no effect.
  • If the API key credential is missing or invalid, authentication errors will occur. Confirm the credential is correctly configured in n8n.

Discussion