Overview
This node enables sending SMS messages through a selected SMS provider and campaign. It is designed to send personalized SMS content to multiple users, supporting dynamic message templating with data from previous workflow nodes. The node can optionally wait until all messages are sent before continuing the workflow, ensuring synchronous operation when needed.
Common scenarios include:
- Marketing campaigns where personalized SMS messages are sent to a list of users.
- Notification systems that require sending SMS alerts based on workflow data.
- Customer engagement workflows that tag users or limit message frequency per mobile number.
Example: Sending a promotional SMS to users in a campaign, using their first names dynamically inserted into the message text.
Properties
| Name | Meaning |
|---|---|
| Select a Campaign | Choose a campaign from a dynamically loaded list of available campaigns. |
| SMS Provider | Select an SMS service provider from a dynamically loaded list. |
| SMS Name | Name identifier for the SMS message being sent. |
| SMS Message | The text content of the SMS, supports dynamic placeholders referencing previous node data. |
| Wait Until All Messages Sent. | Boolean flag to wait for confirmation that all SMS messages have been sent before proceeding. |
| Add Tag | Optional tag name to add to users receiving the SMS. |
| Once Per Mobile Number | Boolean to restrict sending the SMS once per mobile number. |
| When Can Users Receive Again (In days, 0 for never)? | Number of days after which users can receive the SMS again if restricted by "Once Per Mobile Number". |
| Ignore FC | Boolean flag, purpose not explicitly detailed but likely related to ignoring some filter/check. |
| Users | Optional string to specify users; if left blank, uses users from previous node input. |
Output
The node outputs JSON data representing the response from the SMS sending API. If waiting for all messages to be sent, it returns the final status of the batch send operation. Otherwise, it returns the immediate response from the SMS batch request.
The output JSON includes details such as:
- Confirmation of SMS send requests.
- Status of message delivery if waiting is enabled.
- Any errors or metadata returned by the external SMS service.
No binary data output is produced by this node.
Dependencies
- Requires access to an external API endpoint defined by environment variable
CDP_URL. - Requires an API key credential provided via environment variable
UNEXO_API_KEYfor authorization. - Uses HTTP requests to interact with the external SMS and campaign management services.
- Relies on n8n's helper methods for HTTP requests and expression evaluation.
Troubleshooting
- API Authentication Errors: Ensure the environment variable for the API key is correctly set and valid.
- Campaign or Provider Loading Issues: Verify that the external API endpoints for campaigns and SMS providers are reachable and returning expected data.
- Message Templating Errors: Incorrect or missing placeholders in the SMS message may result in empty or malformed messages. Confirm that referenced fields exist in previous node data.
- Timeouts Waiting for Messages: If "Wait Until All Messages Sent" is enabled, network delays or API issues might cause timeouts. Adjust retry logic or disable waiting if synchronous confirmation is not required.
- Maximum Retry Attempts Reached: Indicates the node waited for message completion but did not receive confirmation within allowed retries. Check API health and connectivity.
Links and References
- No direct external links provided in the source code.
- Refer to your SMS provider's API documentation for details on message sending and status checking.
- Consult n8n documentation for usage of expression syntax and HTTP request helper methods.