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 send email notifications. Specifically, the "Send Email" operation under the "Notification" resource allows users to send customized email messages to one or more recipients. This is useful in scenarios such as notifying clients or team members about updates related to missions, tasks, or other events managed within Everest TMS.
Practical examples include:
- Sending mission status updates to clients.
- Alerting agents or staff about new assignments.
- Distributing general announcements or reminders via email.
Properties
| Name | Meaning |
|---|---|
| Email Addresses | Comma-separated list of email addresses to which the notification emails will be sent. |
| Message Text | The body of the email message supporting line breaks and placeholders like [mission_ref], [client_lastname] for dynamic content insertion. |
| Mission Reference | A string value used to replace the [mission_ref] placeholder in the message text, typically a mission identifier. |
Output
The node outputs a JSON array where each element corresponds to the result of sending an email notification for each input item processed. The structure of each output object depends on the response from the Everest TMS API but generally includes confirmation details of the sent email.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Everest TMS API using an API key credential configured in n8n.
- The node relies on the Everest TMS backend services to process and send email notifications.
- Proper configuration of the Everest API credentials in n8n is necessary for authentication.
Troubleshooting
Common Issues:
- Invalid or missing email addresses can cause the operation to fail.
- Incorrect or missing API credentials will prevent communication with Everest TMS.
- Placeholders in the message text that do not have corresponding property values may remain unreplaced.
Error Messages:
- Errors related to authentication usually indicate misconfigured or expired API keys; verify and update credentials.
- Validation errors about email format or missing required fields suggest checking the input properties.
- Network or service unavailability errors require checking the connectivity to Everest TMS.
Links and References
- Everest TMS official documentation (for API and email notification features)
- n8n documentation on creating and configuring API credentials
- General best practices for email formatting and placeholder usage