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 "Create Event" operation on the Contact resource allows users to log or register specific events related to a contact within the Everest Transport Management System (TMS). This node is useful for tracking interactions and activities such as when a contact is created, updated, an email is sent or opened, a form is submitted, phone calls occur, or custom events happen.
Practical examples include:
- Automatically logging when a new contact is added to the system.
- Recording when an email campaign reaches a contact (email sent/opened).
- Tracking inbound or outbound phone calls with contacts.
- Adding notes or descriptions about conversations or meetings with contacts.
This helps maintain a detailed history of contact-related activities, which can be valuable for customer relationship management, auditing, or triggering further automation.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier number of the contact for whom the event is being created. |
| Event Type | The category/type of event to create. Options: Contact Created, Contact Updated, Email Sent, Email Opened, Form Submitted, Custom, Phone Call Incoming, Phone Call Outgoing. |
| Description | A textual description providing additional details about the event, e.g., notes from a conversation. |
Output
The node outputs a JSON array where each element corresponds to the result of creating an event for a contact. The structure typically includes confirmation details of the created event, such as event ID, type, timestamp, and any other metadata returned by the Everest TMS API.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Everest TMS API via an API key credential configured in n8n.
- The node depends on the Everest API endpoints to create contact events.
- Proper permissions on the Everest account are necessary to create events on contacts.
Troubleshooting
Common Issues:
- Invalid or missing Contact ID: Ensure the Contact ID provided exists in the Everest system.
- Unauthorized errors: Verify that the API key credential has sufficient permissions.
- Network or API downtime: Check connectivity and Everest service status.
Error Messages:
"Contact not found": The specified Contact ID does not exist; verify the ID."Invalid event type": The event type selected is not recognized; choose a valid option."Authentication failed": The API key is invalid or expired; update credentials.
To resolve these, double-check input parameters, ensure credentials are correct, and confirm the Everest API is reachable.
Links and References
- Everest TMS official API documentation (for event creation and contact management)
- n8n documentation on setting up API credentials and using HTTP request nodes (general guidance)