Overview
This node, named "One Time Send Content - UNEXO," is designed to send a single batch of content to a selected user segment through various communication channels such as SMS, WhatsApp, WebPush notifications, or Email. It is useful in marketing automation and customer engagement scenarios where you want to target a specific group of users with a campaign message or notification only once.
Typical use cases include:
- Sending promotional SMS messages to a targeted customer segment.
- Delivering WhatsApp campaign messages to subscribers.
- Pushing web notifications for announcements or offers.
- Dispatching email campaigns using predefined templates.
The node supports selecting the segment, campaign, content template, and provider dynamically, allowing flexible targeting and content delivery.
Properties
| Name | Meaning |
|---|---|
| Select A Segment | Choose a user segment from a list to which the content will be sent. |
| Select a Campaign | Choose a campaign from the available campaigns. |
| Content Type | Select the type of content to send: SMS, WhatsApp, WebPush, or Email. |
| Select a Content Template of the Campaign | Choose a content template associated with the selected campaign and content type. |
| Select Provider | Choose the content delivery provider based on the campaign, content template, and content type. |
| Check And Add Tag | Specify a tag name to check and add to the users when sending content. |
| Once Per Mobile Number | Boolean flag indicating whether to send the content only once per mobile number (true/false). |
| Ignore FC | Boolean flag to ignore some internal filtering condition (exact meaning depends on backend logic). |
Output
The node outputs a JSON array containing the response from the content sending API call. The structure of the output JSON depends on the external service's response but generally includes information about the batch sending status, success or failure details, and any relevant metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an environment variable
CDP_URLthat points to the base URL of the external content delivery platform. - Requires an environment variable
UNEXO_API_KEYused as a Bearer token for authorization in all API requests. - Relies on several REST API endpoints provided by the external platform to:
- Fetch segments, campaigns, content templates, and providers.
- Calculate delay before sending content.
- Send batch content via SMS, WhatsApp, WebPush, or Email channels.
Troubleshooting
Common issues:
- Missing or incorrect environment variables (
CDP_URL,UNEXO_API_KEY) will cause authentication or connection failures. - Selecting invalid or unavailable segments, campaigns, or templates may result in empty lists or errors.
- Network connectivity problems can prevent API calls from succeeding.
- If the "Once Per Mobile Number" option is enabled, ensure the backend supports deduplication; otherwise, some users might not receive messages.
- Missing or incorrect environment variables (
Error messages:
- Authorization errors typically indicate invalid or missing API keys.
- HTTP 404 or 400 errors may occur if the selected segment, campaign, or template IDs are invalid.
- Timeout or delay calculation failures could happen if the delay endpoint is unreachable.
Resolutions:
- Verify environment variables are correctly set in n8n.
- Confirm the selected options exist and are valid in the external system.
- Check network access and API availability.
- Review API key permissions and regenerate if necessary.
Links and References
- No direct links are embedded in the code. For more information, consult the documentation of the external content delivery platform referenced by the environment variables.