Xponent Messaging

The Xponent Messaging Node is a native node that simplifies SMS, MMS, and RCS communications within orchestration graphs. It enables users to trigger immediate or scheduled messaging communications by selecting approved SMS, MMS, and RCS 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.

The Xponent Messaging Node icon changes dynamically to reflect its current configuration status, providing a visual indication of node action, whether the node is added or configured to send a message immediately, schedule a message, or cancel a scheduled message.

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-tim setup.

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

• Approved Messaging Templates on XCC Platform: Only approved 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 approved 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 approved 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 approved 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 approved template from the list.

Mapping Parameters

If there are template‑specific parameters, they will be listed immediately below the template name. You must map each parameter to a corresponding value from the graph schema to ensure that the message content is populated correctly during execution.

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 selecting a messaging template, the Messaging Node displays the Template Name and Channel Type (SMS, MMS, or RCS).

Send Configuration

Use the Send option to deliver SMS, MMS, or RCS communications immediately or schedule them for future delivery. Configure the communication channel, template, recipients, identifiers, return values, expiration settings, callbacks, and postback options to meet your messaging requirements.

All template-specific parameters defined in the XCC template are displayed below the template name and are available for mapping.

For Example: FIRST_NAME, LAST_NAME, DATE

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.

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

• 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.

• Identifiers:  Specifies the profile identifier used to associate the communication with a customer profile. This value is automatically selected and cannot be modified. The identifier is used to store communication details, including communication history and reference IDs, at the profile level.

Immediate Delivery

Use the Immediate Delivery configuration to send a message as soon as the Messaging Node is executed.

Delivery and Callbacks (Optional)

Use the Delivery and Callbacks section to configure message expiration and callback settings for SMS, MMS, and RCS communications.

• Expiration Settings: Expiration settings define when a message is no longer eligible for delivery if it has not yet been delivered.

  • Expire After (Relative): Specifies a relative expiration period from the time the message is created. Enter a numeric value followed by a supported time unit.

    For Examples: 30s = 30 seconds, 2m = 2 minutes, 1h = 1 hour

  • Expire at Specific Time (Absolute): Specifies the exact date and time when the message expires. The value must be provided in ISO 8601 format.

    For Example: 2025-06-10T18:00:00

• Callbacks: Configure callback URLs to receive communication-related events.

  • Receipt URL: Specifies the endpoint that receives delivery receipt notifications for the communication.

  • Reply URL: Specifies the endpoint that receives customer reply notifications for the communication.

    

• Postback: Postback data is sent only when a Receipt URL or Reply URL is configured. The value must be valid JSON.

  • Postback Data: Specifies the JSON payload that is included with callback notifications.

• Field Count: When one or more fields are configured under optional Delivery and Callbacks, a count badge is displayed on the section header to indicate the number of configured fields.

  

• Clear Parameter: The Clear Parameters button becomes available when one or more optional fields contain values. Select this button to remove all configured override values and revert to the template defaults.

  • Undo - Appears after selecting Clear Parameters. Use this option to restore the most recently cleared configuration values.

    

• Preview Template: This displays a preview of the selected message template. Here you can review the template content before configuring or deploying the message Node.
  

Scheduled Delivery

Use the Scheduled Message option to send a message at a future date and time. Scheduled emails are useful for time-based communications such as payment reminders, registration prompts, and follow-up notifications.

Scheduled communications can be configured using either a relative delay or a specific delivery date and time, and can be canceled later using the communication reference ID.

• Send After (Relative): Specifies a relative delay before the message is sent. Enter a numeric value followed by a supported time unit.

  For Examples: 30s = 30 seconds, 2m = 2 minutes, 1h = 1 hour

  

  If both Send After (Relative) and Send at Specific Time (Absolute) are configured, the Send After (Relative) value takes precedence.

• Send at Specific Time (Absolute): Specifies the exact date and time when the message should be delivered. The value must be provided in ISO 8601 format and include a time zone offset.

  For Example: 2025-06-10T18:00:00-06:00

  

   If the Send at Specific Time (Absolute) value is set to a date and time in the past, the communication is sent immediately.

• Delivery and Callbacks: Scheduled messages support the same Delivery and Callbacks (Optional) configuration options as immediate messages. Refer to Immediate Delivery and Callbacks (Optional) for configuration details.

• Clear Parameter: The Clear Parameters button becomes available when one or more optional fields contain values. Select this button to remove all configured override values and revert to the template defaults.

  • Undo - Appears after selecting Clear Parameters. Use this option to restore the most recently cleared configuration values.

• Preview Template: This displays a preview of the selected message template. Here you can review the template content before configuring or deploying the Messaging Node.

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.

Cancel Scheduled Message

Use the Cancel option to cancel a previously scheduled message communication. To cancel a scheduled message, provide the communication reference ID and any additional information required by the communication platform.

When a scheduled message is created, communication details, including the communication reference ID, type of delivery are stored in the profile's communication history. Use this Reference ID (communicationId) when configuring the Cancel Scheduled Message action

• Reference ID: Specifies the unique communication reference associated with the scheduled message. This value is used to identify the scheduled communication that should be canceled.

• Return Value: Specifies the schema location where the cancellation response is stored.

 Handling Approved Template Changes After Deployment

If the approved 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

• For existing Messaging Node implementations created before 26.2, ensure a valid Identifier is configured in the graph before invoking the communication node. Communication nodes require a profile identifier to store communication details against the customer profile. Existing graphs should be updated accordingly to avoid communication processing issues.

• We recommend promoting new messaging template versions to approved 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 approving the updated template. This approach helps avoid disruption for deployed graphs.

• Use Relative Scheduling for recurring or dynamic date-based use cases to reduce the risk of configuring past delivery dates. When configuring scheduled emails, ensure that the delivery date and time are valid and in the future. Past-dated schedules may not behave as expected depending on the underlying communication platform.

• Preview the selected template before deployment to verify content and parameters.

FAQ