Send Content - Captain
AI-generatedOverview
This node sends content messages through various communication channels such as SMS, WhatsApp, WebPush, Email, and Bale within a selected campaign. It allows users to select a campaign, content type, and content template, and configure sending options like provider selection, rotary mode for WhatsApp, tagging settings, and message sending constraints. The node supports waiting until all messages are sent before proceeding and handles retries for sending requests. It is useful for automating and managing bulk message sending in marketing or communication workflows.
Use Case Examples
- Sending an SMS campaign to a list of users with a specific content template.
- Sending WhatsApp messages in rotary mode to distribute load across providers.
- Sending WebPush notifications with tagging and timing controls.
Properties
| Name | Meaning |
|---|---|
| Select a Campaign | Select a campaign from the list to send content for. |
| Content Type | Select the type of content to send (SMS, WhatsApp, WebPush, Email, Bale). |
| Select a Content Template of the Campaign | Select a specific content template from the chosen campaign and content type. |
| Rotary Mode | Enable rotary mode for WhatsApp to distribute messages across providers. |
| Select Provider | Select a specific provider for sending content, hidden if rotary mode is enabled. |
| Wait Until All Messages Sent. | Wait for all messages to be sent before proceeding. |
| Tag Settings | Settings for checking, adding, and removing tags on users with timing controls. |
| Once Per Mobile Number | Send content only once per mobile number. |
| When Can Users Receive Again (In days, 0 for never)? | Number of days after which users can receive content again if once per mobile number is enabled. |
| Ignore FC | Ignore FC (possibly a filter or condition) when sending. |
| Ignore DND | Ignore Do Not Disturb settings when sending. |
| Users | Specify users to send content to; leave blank to use users from the previous node. |
Output
JSON
response- Response from the content sending API indicating the result of the send operation.
Dependencies
- Requires an API key credential for authorization (UNEXO_API_KEY).
- Requires environment variable CDP_URL for API endpoint base URL.
Troubleshooting
- Common issues include API request failures due to network issues or invalid API keys, which result in retry attempts and error logs.
- If the node fails after maximum retry attempts, check the API key validity and network connectivity.
- Ensure the selected campaign, content type, and template exist and are correctly loaded via the provided methods.