Xponent Messaging

The Xponent Messaging Node is a native node that simplifies SMS and MMS communications within orchestration graphs. It enables users to trigger messaging communications by selecting active SMS or MMS templates maintained in XCC (Xponent Communication Control), without relying on custom REST connectors or external integrations. This capability streamlines configuration and reduces implementation complexity.

This section provides a detailed explanation of how to add the Messaging Node to your orchestration graph, configure it correctly, and handle key scenarios before and after graph deployment.

RCS support will be available in a future release.

Prerequisites

• XCC Account Configuration: The XCC account must be properly integrated with Xponent. Without this integration, messaging templates cannot be retrieved.

  

   Please contact your administrator for one-time setup.

• Xponent Messaging Account Configuration: The Xponent Messaging Account should be configured and active to enable SMS and MMS communication within orchestration graphs. (Please contact your administrator for one-time setup.)

• Active Messaging Templates on XCC Platform: Only active state templates will appear in the template selection list.

Adding Node to the Graph

Insert the Xponent Messaging Node into your orchestration graph

1. Right-click anywhere on the blank space within the graph canvas and select Add Node to Graph from the context menu that appears.

2. When the node selection panel opens, under the Base Nodes, locate and select the Xponent Messaging node.

3. Click Add Node. This action will place the Xponent Messaging node in your graph.

Selecting XCC Account

Before you can configure the node, it is essential to confirm that your XCC Account is integrated with Xponent. If the integration is already in place, you will notice an XCC Account dropdown displayed in the bottom-right corner of the Edit Xponent Messaging node panel. This dropdown allows you to select the appropriate XCC Account for access to messaging templates.

If the XCC Account integration has not been completed, the system will display an error message stating: “Account credentials are missing or invalid. Contact administrator.”

This message indicates that the node cannot retrieve messaging templates because the account credentials are either missing or incorrect.

 You must contact your administrator to configure the XCC Account and Xponent Messaging Account.

Once the administrator completes the setup, the message will disappear, and the XCC Account dropdown will become available for use.

  For Administrators: Refer to the articles on configuring XCC Account and Xponent Messaging Account for detailed steps.

Selecting a Messaging Template

1. Under XCC Account, select the required XCC account and Configuration ID from the dropdown.

2. Click on the Add+ button to select an active messaging template from the chosen account. A new window will open displaying messaging templates for the selected XCC account.
   

3. If no templates are available, you will see the message: “Templates from this account will appear here when available. If you believe templates should be available, please contact your administrator.” In this case, contact your administrator and update the account as needed.
   

4. Once messaging templates are available, the list will show only the most recent active version of each messaging template to ensure accuracy and compliance.

5. When selecting a messaging template, the system displays a list of templates available for the selected XCC account. Each template entry includes the following information, which helps confirm that you are selecting the correct messaging template version:

   • Template Name

   • Channel (SMS, MMS, or RCS)

   • Version number

   • Last Modified date

   

6. At the top of the template list, the Messaging Node provides buttons to filter by SMS, MMS, and RCS, making it easier to focus on a specific messaging template type:

   • Select any one channel to filter templates by message type.

   • Selecting the same button again removes the filter and displays templates for all channels.

   

7. You can search for a required template by entering the template name in the search (Find) box. Templates with matching or partially matching names are displayed in the list.

   • If no templates match the entered search text, the system displays the message: “Check for typos or try different keywords.” Update the search criteria to find the required template.

   

8. The Messaging Node provides multiple ways to preview messaging templates:

   • Selected template preview: After you select a template, its preview is displayed on the right‑hand side of the template page.

   • Preview (👁️) icon: Selecting the preview icon opens a pop‑up window showing the template preview without changing the current selection.

     This allows you to compare the currently selected template with other templates by opening pop‑up previews without removing or changing the active template selection.

   

9. After selecting a template, it is applied directly to the node, and the template details are displayed under the selected XCC account.

   To change the template, click the selected template field and choose a different active template from the list.

Mapping Parameters

After selecting a messaging template, the Messaging Node displays the template name and channel type (SMS, MMS, or RCS). Also, all template‑specific parameters defined in the XCC template are displayed below the template name and are available for mapping.

Template‑specific parameters must be mapped for the node to be valid. For Example, BRAND, FIRST_NAME, LAST_NAME, DATE

 You must map each parameter to a corresponding value from the graph schema to ensure that the messaging content is populated correctly during execution.

If the selected messaging template defines no placeholders in XCC, a note will appear at the bottom of the list of parameters stating: “This template has no additional configurable parameters.” The node still includes required system fields, such as the Recipient Phone Number and Node Return Value.

In addition to template‑specific parameters, the Messaging Node always displays required system and optional fields

Required system fields:

• Recipient Phone Number: A required system field that specifies the destination phone number to which the SMS or MMS message is sent.

• Node Return Value: A system‑generated output that captures the response returned by the messaging platform after message execution, such as a reference or transaction identifier.

Optional system fields:

• Receipt URL (Optional): Invoked when the message is successfully delivered.

• Reply URL (Optional): Invoked when a recipient replies to the message.

• Postback Data (Optional): Postback data is sent only when a Receipt URL or Reply URL is configured. The value must be valid JSON. Only simple key‑value JSON is supported.

How to map parameters:

• First, select the schema you want to use for mapping.

• Click the arrow next to the parameter to map the schema to it. Once mapped, the schema details will appear within the parameter field.

After confirming the details, proceed to deploy the graph. Deployment applies the selected messaging template and mapped parameters to the messaging execution process, ensuring accurate and compliant communication.

 Handling Active Template Changes After Deployment

If the active messaging template changes after the graph has been deployed and new parameters are introduced, you must coordinate with your Xponent team to map these parameters and redeploy the graph. Failure to do so will result in graph execution errors because the system cannot process a template with unmapped parameters.

Changing the XCC Account

When you select a different XCC account in the Messaging Node, any previously selected template is no longer applicable. You must select a new template from the newly selected XCC account and map its parameters before the node can be used.

• Messaging templates are scoped to the selected XCC account. Templates and parameter mappings cannot be retained when switching accounts.

Best Practices

• We recommend promoting new messaging template versions to active only if the template has visual changes. If new parameters are introduced in the process, clone the template and create a new one instead of making the updated template active. This approach helps avoid disruption for deployed graphs.