Overview
This node, named "PRO Send Email - UNEXO," is designed to send personalized email campaigns to users. It integrates with an external campaign and email provider system via API calls. The node supports selecting a campaign and an email provider, composing the email content dynamically using expressions, and sending emails in batches.
Common scenarios where this node is beneficial include:
- Sending marketing or promotional email campaigns to targeted user groups.
- Personalizing email content based on user data from previous workflow nodes.
- Managing email frequency with options like "once per email" and "do not disturb" time windows to avoid spamming users.
Practical example:
You have a list of users with their first names from a previous node. You want to send them a promotional email campaign with a subject line and preview text personalized with their first name. You select the campaign and email provider, compose the email content using expressions referencing user data, and send the batch while respecting quiet hours (e.g., no emails sent between 10 PM and 9 AM).
Properties
| Name | Meaning |
|---|---|
| Select a Campaign | Choose a campaign from the available list fetched dynamically from the external service. |
| Email Provider | Select the email provider from a dynamically loaded list. |
| Email Name | Name of the email campaign being sent. |
| Sender Name | The sender's display name shown in the email (default: "Tom from UNEXO"). |
| Subject | Subject line of the email; supports dynamic expressions to personalize per user. |
| Preview | Preview text of the email; supports dynamic expressions for personalization. |
| Email Content | Main content/body of the email; supports dynamic expressions for personalization. |
| Users | String input specifying users to send to; if left blank, uses users from the previous node. |
| Once Per Email | Boolean flag indicating whether each user should receive the email only once. |
| When Can Users Receive Again (In days, 0 for never)? | Number of days before a user can receive the same email again if "Once Per Email" is enabled. |
| Dont Disturb | Boolean flag to enable quiet hours during which emails are delayed (default: true). |
Output
The node outputs a JSON array containing the response from the external email sending API. This response typically includes information about the success or failure of the batch email send operation.
The output JSON structure corresponds directly to the API response and may contain details such as:
- Status of the email batch send.
- Any errors or messages returned by the API.
- Metadata about the processed users or emails.
No binary data output is produced by this node.
Dependencies
Requires environment variables:
CDP_URL: Base URL of the external campaign management API.UNEXO_API_KEY: API key used for authorization with the external service.
The node makes HTTP requests to the external API endpoints:
- To fetch campaign names:
${CDP_URL}/api/campaigns/campaignNames - To fetch email providers:
${CDP_URL}/api/projects/listEmailProviderTitles - To send email batches:
${CDP_URL}/api/users/sendEmailBatch
- To fetch campaign names:
Proper configuration of these environment variables and valid API credentials are necessary for the node to function correctly.
Troubleshooting
Emails not sending or API errors: Verify that the
CDP_URLandUNEXO_API_KEYenvironment variables are correctly set and valid. Check network connectivity to the API endpoints.Empty campaign or provider lists: If the dropdowns for campaigns or email providers do not populate, ensure the API key has sufficient permissions and the external service is reachable.
Delayed email sending due to "Dont Disturb": The node enforces a quiet period between 10 PM and 9 AM local time. Emails triggered during this window will be delayed until 9 AM. This behavior is intentional to avoid disturbing recipients at night.
Dynamic expressions not resolving: Ensure that the expressions used in Subject, Preview, and Content fields reference valid data from previous nodes. Incorrect or missing references may result in placeholders being sent literally.
Once Per Email logic issues: If users receive duplicate emails despite enabling "Once Per Email," verify the correct setting of the "When Can Users Receive Again" parameter and confirm that user identifiers are consistent.
Links and References
- n8n Documentation on Expressions
- HTTP Request Node Documentation
- External API documentation would be required for full details but is not included here.