PRO Send SMS - Captain icon

PRO Send SMS - Captain

Node to Send SMS - Captain

PRO Send SMS - Captain

AI-generated

Overview

This node sends SMS messages to users as part of a campaign using a selected SMS provider. It supports dynamic message content with placeholders, tag management for users, and options to control message sending frequency and conditions. It is useful for marketing campaigns, notifications, or any scenario requiring bulk personalized SMS delivery.

Use Case Examples

  1. Sending a personalized SMS campaign to a list of users with dynamic placeholders for names.
  2. Using tag settings to add or remove tags from users based on SMS sending status.
  3. Controlling SMS sending frequency to avoid sending multiple messages to the same mobile number within a specified period.

Properties

Name Meaning
Select a Campaign Select a campaign from the list to associate the SMS messages with.
SMS Provider Select the SMS provider from the list to send messages through.
SMS Name Name of the SMS message for identification.
SMS Message The content of the SMS message, supports dynamic placeholders for personalization.
Wait Until All Messages Sent. Boolean flag to wait until all SMS messages are sent before continuing.
Tag Settings Settings to check for a tag on users, add it if missing, and specify when to remove it (days, hours, minutes).
Once Per Mobile Number Boolean flag to send the SMS only once per mobile number.
When Can Users Receive Again (In days, 0 for never)? Number of days to wait before allowing the same user to receive another SMS if 'Once Per Mobile Number' is enabled.
Ignore FC Boolean flag to ignore FC (possibly a filter or condition related to sending).
Ignore DND Boolean flag to ignore Do Not Disturb settings when sending SMS.
Users A string of users to send SMS to; if left blank, users from the previous node are used.

Output

JSON

  • providerTitle - The SMS provider used for sending messages.
  • usersAndText - Array of user objects with userId, personalized text message, and output result.
  • campaign_id - The ID of the campaign associated with the SMS messages.
  • smsName - The name of the SMS message.
  • once - Flag indicating if the SMS is sent once per mobile number.
  • onceDaysToRemove - Number of days before a user can receive the SMS again if 'once' is true.
  • uuid - Unique identifier for the batch of SMS messages sent.
  • ignoreFC - Flag indicating whether to ignore FC conditions.
  • ignoreDND - Flag indicating whether to ignore Do Not Disturb settings.
  • executionId - The execution ID of the workflow run.
  • workflowName - The name of the workflow executing the node.
  • tagName - The tag name to check and add to users if missing.
  • tagToRemoveDays - Days after which the tag should be removed.
  • tagToRemoveHours - Hours after which the tag should be removed.
  • tagToRemoveMinutes - Minutes after which the tag should be removed.

Dependencies

  • Requires environment variables CDP_URL and UNEXO_API_KEY for API endpoint and authentication.

Troubleshooting

  • Common issues include API request failures due to incorrect or missing environment variables (CDP_URL, UNEXO_API_KEY).
  • Network errors or timeouts when sending or checking SMS batch status may occur; the node retries requests multiple times with delays.
  • If the SMS message contains dynamic placeholders, ensure the referenced data exists in the input items to avoid empty replacements.
  • Waiting for all messages to be sent may cause long execution times depending on batch size and API response delays.

Links

Discussion