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 create new contact entries. It is useful for automating the addition of contacts into the Everest CRM, such as when onboarding new clients or partners, or syncing contact data from other systems.
Practical examples include:
- Automatically adding a new customer’s contact details after a form submission.
- Importing phone and email information for logistics agents or clients into Everest.
- Enriching contact records with additional metadata like job title or company during creation.
Properties
| Name | Meaning |
|---|---|
| The email address of the contact to be created. | |
| Phone | The phone number of the contact to be created. |
| Additional Fields | Optional extra fields to provide more details about the contact: |
| - First Name | Contact's first name. |
| - Last Name | Contact's last name. |
| - Company | Company associated with the contact. |
| - Job | Job title of the contact. |
| - Points | Numeric CRM points assigned to this contact (default is 0). |
Output
The node outputs an array of JSON objects representing the newly created contact(s) in Everest TMS. Each object contains the contact details as stored in the system, including any IDs or metadata returned by the API.
If binary data were involved (not applicable here), it would typically represent files or attachments related to the contact.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node uses the Everest API endpoints internally to perform operations.
- No additional external dependencies are needed beyond the configured API credentials.
Troubleshooting
Common issues:
- Missing required fields such as Email or Phone will cause the operation to fail.
- Invalid phone number or email format might be rejected by the API.
- Network or authentication errors if the API key is invalid or expired.
Error messages:
"Missing required parameter": Ensure all mandatory fields are provided."Authentication failed": Verify that the API key credential is correctly set up."Invalid input data": Check the formatting of email and phone fields.
To resolve errors, double-check input values, ensure credentials are valid, and confirm network connectivity.
Links and References
- Everest TMS official API documentation (refer to your internal or vendor-provided docs).
- n8n documentation on creating custom nodes and using API credentials.