Overview
This node sends email notifications using the 97Display notification API. It supports sending emails either by selecting a predefined email template or by manually specifying the subject and body content. The node is useful in workflows where automated email communication is required, such as notifying users about events, sending alerts, or delivering personalized messages based on workflow data.
Practical examples:
- Sending welcome emails to new users with a selected email template.
- Dispatching custom alert emails with dynamic subject and body without using templates.
- Integrating with external systems that trigger email notifications based on webhook data.
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 internally for tracking and API requests. |
| Use Email Template? | Boolean option to choose between sending an email via a predefined template (true) or manual entry (false). |
| Email Template | Dropdown list of available email templates loaded dynamically from the API; required if using templates. |
| Subject | Subject line of the email; required if not using a template. |
| Body | Body content of the email; required if not using a template. Supports multiline text input. |
| Is HTML Email | Hidden boolean indicating whether the email should be sent as HTML (default is plain text). |
| APIKey | Hidden field containing the API key for authenticating requests to the 97Display notification API. |
Output
The node outputs an array of JSON objects, each representing the response from the 97Display notification API for each input item processed. Each output JSON contains the API's response data confirming the email send status or error details if any occurred.
No binary data output is produced by this node.
Dependencies
- Requires access to the 97Display notification API endpoint at
https://notificationapi.api97.com. - Needs a valid API key credential configured in the environment variable
MY_API_KEYfor authentication. - Relies on webhook input data providing fields like
OrganizationId, recipient email, names, and tokens. - Uses dynamic loading of email templates from the API based on the current workflow ID.
Troubleshooting
Common issues:
- Failure to load email templates due to invalid API key or network issues.
- Errors when parsing the selected email template JSON string.
- Missing required fields such as recipient email or subject/body when not using templates.
- API request failures due to incorrect API key or endpoint unavailability.
Error messages and resolutions:
"Error loading templates: <message>": Indicates failure fetching templates; verify API key and network connectivity.- JSON parse errors on template selection: Ensure the template value is a valid JSON string or a correct template ID.
- API response errors: Check that the API key is valid and has sufficient permissions; confirm all required email fields are provided.
- If the node throws errors but "Continue On Fail" is enabled, it will output error details per item instead of stopping execution.
Links and References
- 97Display Notification API Documentation (assumed public API docs)
- n8n documentation on Creating Custom Nodes
- n8n expression syntax guide for Accessing Webhook Data