Google Business Messages Node

Webex Connect allows you to configure Google Business Messages prebuilt node for sending Text messages, Images, Standalone Rich Card, and Carousel Rich Cards. Suggestions can be sent with any of these message types.

Prerequisites

  • You must have a Google Business Messages account and at least 1 agent onboarded with Google Business Messages.
  • To add your own Google Business Messages asset on Webex Connect or to create a new Google Business Messages account through Webex Connect (Messaging Service Partner), please refer to this page for instructions - Google Business Messages

Node Configuration - Generic

Please note that the procedure common to all message types is described below. For step 6, follow the specific procedure based on the type of message you select.

Drag-and-drop the node onto the visual flow builder and double-click the node to configure it.

  1. Select Send Message under the Method Name drop-down list box.
  2. Enter the Conversation ID in the To field.
  3. Select one of the following options in the Representative Type field:
    1. Human
    2. Bot
  4. Enter the representative name in the Representative Display Name field.
  5. Enter the thumbnail image URL for Representative Avatar Image.
  6. In the Message Configuration, follow one of the procedures below depending on the Message Type selected.
  7. In the Message Suggestions (Optional) section:
    1. Suggestion Type: Select from:
      1. Reply: Select this option to configure data to be displayed on the user’s screen when they send an initial query to the business.
      2. Action: Select this option to configure data to be displayed for perform an action based on the user’s initial query.
      3. Live Agent Request: This option is not displayed when the Representative Type selected is Human. Select to configure data for transferring the query to a live agent.
    2. Reply Text: Displayed when the Suggestion Type selected is Action or Reply. Enter text to be displayed on a button on the user’s device.
    3. Action Type: Displayed only when the suggestion type Action is selected.
      1. Open URL: Select this option if a URL logon action has to be performed for the user.
        1. URL: Enter the URL to be browsed from the user’s phone.
      2. Dial Action: Select this option if a dial action is to be prompted to the user.
        1. Phone Number: Displayed only when the Action Type selected is Dial Action. Enter the phone number to be patched directly from the user’s screen.
    4. Reply Postback Data: Displayed when the Suggestion Type selected is Action or Reply. Enter text to be posted back to the business in the string format as supportive information to the text added in the Reply Text field.
  8. (Optional) Enter values for the following:
    1. Correlation ID: Unique identifier for the message.
    2. Notify URL: A URL you choose to notify about the delivery status of the message.
    3. Callback Data: Additional data to be sent along with the delivery reports to the URL.
  9. Click Save.

Message Types

Configuring Text

  1. In the Message Configuration section:
    1. Message Type: Select Text.
    2. Text: Enter text to be displayed in your message not exceeding the prescribed 3072 character limit.
    3. Fallback Text: Enter text that should be displayed if the user’s device doesn’t support the message type or content.
    4. (Optional) Select Contains Rich Text if your message contains bold text, hyperlinks, or line breaks.
  2. In the Message Suggestions (Optional) section, configure details if you want to configure reply, action, and live agent request.
  3. Click Save.

Configuring Image

  1. In the Message Configuration section, do the following:
    1. Message Type: Select Image.
    2. Image URL: Paste the image URL.
    3. Thumbnail URL: Paste the thumbnail image URL.
    4. Alt Text: Enter the alternate text to describe details about the media for accessibility purposes.
    5. Force Refresh: Select this option if you would prefer to have the images and data rendered from the server instead of the locally saved cache data in your system, every time you visit the application.
    6. Fallback Text: Enter the fallback text that is displayed if the user's device doesn't support the message type or content.
  2. In the Message Suggestions (Optional) section, configure details if you want to configure reply, action, and live agent request.
  3. Click Save.

Configuring Rich Card

  1. In the Message Configuration section, do the following:
    1. Message Type: Select Rich Card.
    2. Card Content:
      1. Title: Enter the title of the card. Character limit is 200.
      2. Description: Enter the description of the card. Character limit is 2000.
  2. In the Media section:
    1. Image Height: Select the height of the image to be displayed between the options Short, Medium, and Tall.
    2. Image URL: Paste the image URL.
    3. Thumbnail URL: Paste the thumbnail image URL.
    4. Alt Text: Enter the alternate text to describe details about the media for accessibility purposes.
    5. Force Refresh: Select this option if you would prefer to have the images and data rendered from the server instead of the locally saved cache data in your system, every time you visit the application.
    6. Fallback Text: Enter the fallback text that is displayed if the user's device doesn't support the message type or content.
  3. In the Rich Card Suggestions (Optional) section:
    1. Suggestion Type: Select from:
      1. Reply: Select this option to configure data to be displayed on the user’s screen when they send an initial query to the business.
      2. Action: Select this option to configure data to be displayed for perform an action based on the user’s initial query.
    2. Reply Text: Displayed when the Suggestion Type selected is Action or Reply. Enter text to be displayed on a button on the user’s device.
    3. Action Type: Displayed only when the suggestion type Action is selected.
      1. Open URL: Select this option if a URL logon action has to be performed for the user.
        1. URL: Enter the URL to be browsed from the user’s phone.
      2. Dial Action: Select this option if a dial action is to be prompted to the user.
        1. Phone Number: Displayed only when the Action Type selected is Dial Action. Enter the phone number to be patched directly from the user’s screen.
    4. Reply Postback Data: Displayed when the Suggestion Type selected is Action or Reply. Enter text to be posted back to the business in the string format as supportive information to the text added in the Reply Text field.
  4. In the Message Suggestions (Optional) section, configure details if you want to configure reply, action, and live agent request outside of the rich card. For field related information, refer the above step.
  5. Click Save.

Configuring Carousel

  1. In the Message Configuration section, do the following:
    1. Message Type: Select Rich Card.
    2. Card Content:
      1. Title: Enter the title of the card. Character limit is 200.
      2. Description: Enter the description of the card. Character limit is 2000.
  2. In the Media section:
    1. Image Height: Select the height of the image to be displayed between the options Short, Medium, and Tall.
    2. Image URL: Paste the image URL.
    3. Thumbnail URL: Paste the thumbnail image URL.
    4. Alt Text: Enter the alternate text to describe details about the media for accessibility purposes.
    5. Force Refresh: Select this option if you would prefer to have the images and data rendered from the server instead of the locally saved cache data in your system, every time you visit the application.
    6. Fallback Text: Enter the fallback text that is displayed if the user's device doesn't support the message type or content.
  3. In the Carousel Suggestions (Optional) section:
    1. Suggestion Type: Select from:
      1. Reply: Select this option to configure data to be displayed on the user’s screen when they send an initial query to the business.
      2. Action: Select this option to configure data to be displayed for perform an action based on the user’s initial query.
    2. Reply Text: Displayed when the Suggestion Type selected is Action or Reply. Enter text to be displayed on a button on the user’s device.
    3. Action Type: Displayed only when the suggestion type Action is selected.
      1. Open URL: Select this option if a URL logon action has to be performed for the user.
        1. URL: Enter the URL to be browsed from the user’s phone.
      2. Dial Action: Select this option if a dial action is to be prompted to the user.
        1. Phone Number: Displayed only when the Action Type selected is Dial Action. Enter the phone number to be patched directly from the user’s screen.
    4. Reply Postback Data: Displayed when the Suggestion Type selected is Action or Reply. Enter text to be posted back to the business in the string format as supportive information to the text added in the Reply Text field.
    5. In the Message Suggestions (Optional) section, configure details if you want to configure reply, action, and live agent request outside of the rich card. For field related information, refer the above step.
    6. Click Save.

Node Outcomes

Nodes in Webex Connect have one or more outcome edges (that can be used to configure transitions to the next logical node based on the requirements) corresponding to various success or error cases. Some of the standard node outcomes include:

Node Edge (Color)Node OutcomeMeaning
GreenacceptedThe flow exits through this edge when the node executes successfully.
AmberonTimeoutThe flow exits through this edge when message request times out.
RedonErrorThe flow exits through this edge when request processing fails due to an error
RedonInvalidDataThe flow exits through this edge when request processing fails due to missing or invalid data
RedonBadRequestThe flow exits through this edge when request processing fails due to connection error
RedonInternalServerErrorThe flow exits through this edge when request processing fails due to platform error

Differences between a native Send node and a prebuilt integration node

FeatureNative Send NodeSend Node using Pre-built Integration Framework
ThroughputOutbound message requests via native nodes do not count against the Messaging API TPS limitations as that check is bypassed.Utilises Messaging API and hence shares the throughput quota with Messaging API.
ReportingGets associated with the Service in which the flow exists.Same as the native send node.
Ability to Wait for DROffers the ability to wait for DR and add conditional logic based on DR receipt within the configured time limit.The pre-built node doesn’t have this feature for the same reasons as those that apply to Messaging API.
Node ProvisioningControlled through Flow Palette Configurations.Controlled through pre-built integration provisioning framework.
VersioningNot something that we do today though is a technical possibility.Commonly done for nodes built using pre-built integration framework.