Overview
This node sends email notifications using the 97Display notification API. It supports sending emails either by selecting a predefined email template or by specifying a custom subject and body. The node can send emails to either a lead or an organization, based on configuration.
Common scenarios include:
- Automating email notifications triggered by workflows, such as sending welcome emails, alerts, or updates.
- Using predefined templates managed in the 97Display portal for consistent branding and messaging.
- Sending personalized emails to leads or organizational contacts dynamically during workflow execution.
Example use case:
A marketing automation workflow triggers this node to send a promotional email to a lead using a selected email template stored in the 97Display system.
Properties
| Name | Meaning |
|---|---|
| Organization ID | Hidden field automatically populated from webhook data; identifies the organization context. |
| Workflow ID | Hidden field set to the current workflow's ID; used to associate the email with the workflow execution. |
| Use Email Template? | Boolean flag to choose between using a predefined email template (true) or custom subject/body (false). |
| Send To Lead? | Boolean flag indicating whether to send the email to a lead (true) or to the organization (false). |
| Email Template | Dropdown list of available email templates loaded dynamically from the 97Display API; shown if using template. |
| Subject | Custom email subject line; shown if not using a template. |
| Body | Custom email body content; multiline text; shown if not using a template. |
| Is HTML Email | Hidden boolean indicating if the email should be sent as HTML; defaults to false. |
| APIKey | Hidden field containing the API key credential, sourced from environment variables for authentication. |
Output
The node outputs an array of JSON objects, each representing the response from the 97Display API after attempting to send an email for each input item.
Each output JSON contains the API response details about the email sending operation, including success status and any returned metadata.
No binary data is output by this node.
Dependencies
- Requires access to the 97Display notification API endpoint (
https://notificationapi.api97.com). - Needs a valid API key credential configured as an environment variable (
MY_API_KEY) for authenticating API requests. - Relies on dynamic loading of email templates via the API for the "Email Template" property.
- Uses webhook data inputs to populate recipient and contextual information such as email addresses and tokens.
Troubleshooting
- Failed to load email templates: If the node cannot retrieve templates from the API, it will show a placeholder option indicating failure. Check API connectivity and validity of the API key.
- API request errors: Errors during sending emails will throw exceptions unless "Continue On Fail" is enabled, in which case error messages are included in the output JSON. Verify API key permissions and network access.
- Invalid template JSON: If the selected template string cannot be parsed as JSON, the node falls back to using the raw string as the template ID. Ensure templates are correctly formatted.
- Missing required fields: Ensure webhook data includes necessary fields like
Email,FirstName,LastName, and tokens expected by the template.
Links and References
- 97Display Notification API Documentation (assumed official API docs)
- n8n documentation on Creating Custom Nodes
- n8n environment variables setup guide for API keys