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
The node integrates with the Everest Transport Management System (TMS) to perform various operations on different resources. Specifically, for the Contact - Update operation, it updates details of an existing contact in the Everest system. This is useful in scenarios where contact information changes and needs to be kept current, such as updating email addresses, phone numbers, job titles, or CRM points.
Practical examples include:
- Updating a contact’s phone number after receiving new information.
- Modifying the company or job title of a contact when they change roles.
- Adjusting CRM points based on recent interactions or transactions.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to update. |
| Update Fields | Collection of fields to update for the contact. Options include: |
| - Email: Email address of the contact. | |
| - Phone: Phone number of the contact. | |
| - First Name: First name of the contact. | |
| - Last Name: Last name of the contact. | |
| - Company: Company associated with the contact. | |
| - Job: Job title of the contact. | |
| - Points: CRM points assigned to this contact (numeric value). |
Output
The node outputs an array of JSON objects representing the updated contact data returned from the Everest TMS API. Each object contains the contact's updated properties reflecting the changes made.
If the operation involves multiple input items, the output will be an array of corresponding updated contact objects.
No binary data output is indicated for this operation.
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.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Contact ID will likely result in an error from the API indicating the contact was not found.
- Omitting all update fields may cause the operation to do nothing or return an error due to missing data.
- Network or authentication failures can prevent successful API calls.
Error messages:
- Errors related to authentication failure suggest checking the API key credentials.
- Validation errors from the API may indicate incorrect field formats (e.g., invalid email format).
- If the node throws an error about missing required parameters, ensure that Contact ID and at least one update field are provided.
Resolution tips:
- Verify the Contact ID exists in the Everest system before attempting an update.
- Ensure all input fields conform to expected formats.
- Confirm API credentials are valid and have sufficient permissions.
Links and References
- Everest TMS official API documentation (not provided here; consult your Everest TMS provider)
- n8n documentation on creating and using custom nodes and credentials