Send Content - UNEXO icon

Send Content - UNEXO

Node to send a content

Overview

This node, named "Send Content - UNEXO," is designed to send campaign content messages through various communication channels such as SMS, WhatsApp, WebPush, and Email. It allows users to select a campaign, choose the type of content, pick a specific content template, and select a provider for sending the message. The node supports options like waiting until all messages are sent before proceeding, tagging users, controlling message frequency per mobile number, and ignoring certain filters.

Common scenarios where this node is beneficial include:

  • Marketing automation workflows where targeted campaign messages need to be sent to users.
  • Customer engagement processes requiring multi-channel messaging.
  • Sending notifications or promotional content with control over delivery timing and user tagging.

Practical example:
A marketing team wants to send a WhatsApp campaign message using a predefined template to a list of users, ensuring that each mobile number receives the message only once every 7 days, and tagging users who received the message for future segmentation.

Properties

Name Meaning
Select a Campaign Select a campaign from the list of available campaigns.
Content Type Select content type for the campaign. Options: SMS, WhatsApp, WebPush, Email.
Select a Content Template of the Campaign Select a content template associated with the chosen campaign and content type.
Select Provider Select provider from the list, dependent on campaign, content template, and content type.
Wait Until All Messages Sent. Boolean option to wait until all messages are sent before continuing workflow execution.
Check And Add Tag Specify a tag name to check and add to users when sending messages.
Once Per Mobile Number Boolean option to restrict sending messages once per mobile number.
When Can Users Receive Again (In days, 0 for never)? Number of days after which users can receive messages again if "Once Per Mobile Number" is enabled.
Ignore FC Boolean option to ignore a certain filter condition (exact meaning depends on external system).
Users String input specifying users to send messages to; leave blank to use users from previous node output.

Output

The node outputs JSON data representing the result of the send operation. If the "Wait Until All Messages Sent" option is enabled, it waits for completion confirmation and returns the final status of the batch send operation. Otherwise, it returns the immediate response from the send request.

The output JSON includes details such as:

  • Status of the send operation.
  • Any errors or success confirmations.
  • Possibly metadata about the batch or individual messages.

No binary data output is produced by this node.

Dependencies

  • Requires an environment variable CDP_URL which points to the base URL of the external API service.
  • Requires an environment variable UNEXO_API_KEY used as a Bearer token for authorization in API requests.
  • Relies on external REST API endpoints for:
    • Fetching campaigns, content templates, and providers.
    • Sending batch messages via different channels.
    • Calculating delay before sending.
    • Checking completion status of message sending.

Troubleshooting

  • Common issues:

    • Missing or incorrect CDP_URL or UNEXO_API_KEY environment variables will cause authentication or connection failures.
    • Selecting incompatible combinations of campaign, content type, and provider may lead to empty option lists or failed sends.
    • Network or API downtime can cause HTTP request failures.

  • Error messages and resolutions:

    • Authorization errors: Verify that the API key is valid and has necessary permissions.
    • Timeout or maximum retry reached: The node retries checking completion status up to a limit; if exceeded, it logs a message and returns an empty array. Consider increasing timeout or checking API health.
    • Invalid campaign or template IDs: Ensure selected IDs exist and correspond correctly to the campaign and content type.

Links and References

  • No direct links provided in the source code.
  • For more information, consult the documentation of the external API service referenced by CDP_URL.
  • n8n documentation on creating custom nodes and using HTTP Request helper: https://docs.n8n.io/creating-nodes/
  • General info on campaign management and multi-channel messaging best practices.

Discussion