One Time Send Content - Captain icon

One Time Send Content - Captain

Node to send a content once

One Time Send Content - Captain

AI-generated

Overview

This node, named 'One Time Send Content - Captain', is designed to send a content message once to a selected segment of users. It supports multiple content types such as SMS, WhatsApp, WebPush, Email, and Bale. The node allows users to select a segment, campaign, content template, and provider, and includes options for tag management and sending constraints like sending once per mobile number and ignoring certain flags.

Use Case Examples

  1. Sending a promotional SMS campaign to a specific user segment once.
  2. Sending a WhatsApp message to a targeted segment with a specific content template.
  3. Sending a WebPush notification to users in a segment with tag-based conditions.

Properties

Name Meaning
Select A Segment Select a segment from the list to send content to. This is a required field.
Select a Campaign Select a campaign from the list to associate with the content being sent.
Content Type Select the content type for the campaign, such as SMS, WhatsApp, WebPush, Email, or Bale.
Select a Content Template of the Campaign Select a content template associated with the chosen campaign and content type.
Select Provider Select the content provider from the list, dependent on campaign, content selector, and content type.
Tag Settings Settings to check for a tag, add it if it does not exist, and specify when to remove the tag in days, hours, and minutes.
Once Per Mobile Number Boolean flag to send the content only once per mobile number.
Ignore FC Boolean flag to ignore FC (likely a flag or condition related to sending).

Output

JSON

  • response - Response from the content sending API call

Dependencies

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

Troubleshooting

  • Common issues include API request failures due to network issues or invalid API keys. The node retries requests up to 3 times with delays.
  • Error messages related to failed HTTP requests indicate issues with connectivity or authorization. Verify environment variables and API key validity.
  • If no segments, campaigns, or templates load, check API availability and credentials.

Links

Discussion