• com.glide.messaging.awa
• sn_openframe
• sn_cwf_wrkspc
• sn_va_as_service
• com.glide.awa.external

1. In ServiceNow, navigate to All > Scripted REST APIs.
2. Search and open VA Bot Integration record.
3. Edit the record and navigate to the Resources tab and click BOT Integration.
4. Under the Security section, select Requires authentication.
5. Click Update.

Token Verification record

1. In ServiceNow, navigate to All, and then enter token_verification.list in the filter.
2. Click New.
3. Enter the following details in the form:
   • Name – Name of the authentication token, such as Genesys.
   • Description – Description of the authentication token, such as Genesys Digital Messaging Token.
   • Token – Enter an authentication token that you generated using any general programming or script, or click Generate Secure Token in the Related Links. 
4. Click Submit.

Message authentication record

1. In ServiceNow, navigate to All, and then enter message_auth.list in the filter.
2. Click New.
3. Enter the following details in the form:
   • Name – Name of the message authentication, such as Genesys.
   • Provider – Name of the provider, for example Genesys Provider.
   • Inbound message verification – Select the token that you created previously.
   • Outbound message creation – Select the token that you created previously.
4. Click Submit.

1. In ServiceNow, navigate to All, and then enter sys_cs_provider_application.list in the filter.
2. Select and edit the Genesys Cloud Digital Messaging record.
3. Update the following fields:
   • Message Auth – Select the Message Authentication created previously.
   • InboundID – Enter the inbound ID for the messaging platform that you want to use. The inbound ID value must match the value defined in the Unified Experience integration configuration.

     Add the following JSON block to the integration configuration:

     {
       "serviceNowInboundAppIds": {
         "voice": "inbound app ID for voice",
         "messaging": {
           "default": "<fallback inbound app ID for all messaging types>",
           "sms": "<optional> inbound app ID for SMS",
           "line": "<optional> inbound app ID for Line",
           "facebook": "<optional> inbound app ID for Facebook",
           "twitter": "<optional> inbound app ID for X",
           "whatsapp": "<optional> inbound app ID for WhatsApp",
           "instagram": "<optional> inbound app ID for Instagram",
           "webmessaging": "<optional> inbound app ID for Web Messaging",
           "apple": "<optional> inbound app ID for Apple Messaging",
           "open": "<optional> inbound app ID for Open Messaging"
         }
       }
     }
     

     For example, the following illustration shows the attribute mapping configuration in the integration for web messaging. The value of  serviceNowInboundAppIds.messaging.webmessaging is appId2. Enter appId2 as the value for InboundID field.

     Note: You must define a value for default in the attribute configuration to use when no messaging type is configured. If neither a default value nor a messaging type is specified, ServiceNow is the value used by default.

Set up and activate the service channel for messaging in ServiceNow. For more information, see Create or configure a service channel.

1. Log in to ServiceNow.
2. Navigate to  All > Service Channels.
3. Click New.
4. Enter the following information for the service channel:
   • Name –  Name of the service channel to be configured.
   • Inbox Order – The order in which the service channel items appear in the agent inbox.
   • Active – Select the option.
   • Table – Select Interaction [interaction] from the list. 
   • Assign to field – Select Assigned to from the list.
   • Assignment group field – Select Assignment group from the list.
   • Type – Select Messaging from the list.
5. Under the Capacity and Utilization section, enter the following details:
   • Default work item size – Enter 1 as the value.
   • Default capacity – Enter 4 as the value.
   • Utilization condition – Add the following conditions:
     
     • State is not one of Closed Complete and Closed Abandoned
     • Type is Messaging
6. Click Submit.

Before you create external queues:

• Create and configure queues in Genesys Cloud.

Set up external queues in ServiceNow that correspond to Genesys Cloud queues. With the setup of Unified Experience from Genesys and ServiceNow integration, administrators can now create queues in ServiceNow that are externally routed to Genesys Cloud. When you create a queue in ServiceNow, select the following options:

• Service channel – Select the service channel created for the Messaging type.
• Condition mode – Select Simple.
• External – Select this option. Under the External third-party routing section, enter the Genesys Cloud queue ID for Provider queue ID field. For more information, see How can I get the queue ID for my queue in Genesys Cloud?

When integrating Genesys Cloud with ServiceNow, it is important to align agent availability states between the two systems. For more information, see Create presence states in ServiceNow.

For the presence states that match with the Genesys Cloud status, ensure that the service channel created for the Messaging type is added. In the following example, the Chat – Asynchronous is the service channel created for messaging.

Third-party messaging shares the features and capabilities as the other Genesys Cloud messaging channels that use ACD messaging to enable agents to respond to customer interactions. To create and set up the necessary third-party platform integration, perform the following in Genesys Cloud:

1. Create a Messaging Platform Integration in Genesys Cloud. Select the messaging platform for which you want to create an integration. For more information, see Create a platform integration. 
2. Create an inbound messaging flow in Architect. The flow defines the routing logic and queue assignment. For more information, see Add an inbound message flow and Transfer to ACD action. 
3. Create a message routing entry and associate inbound numbers or addresses with an inbound message flow. Select the Messaging Platform integration created for the third-party messaging platform as the inbound address for the inbound message flows. For more information, see Add an inbound message route.

Before configuring the integration, you must set up the necessary divisions in Genesys Cloud based on your organizational structure and routing needs. After you create the divisions, add the relevant division Id to the Unified Experience from Genesys and ServiceNow integration’s advanced configuration.

When you set up the integration in Genesys Cloud, include the divisionIds and specify the appropriate divisions in JSON format. This addition ensures that incoming messages are properly scoped, authenticated, and routed according to the correct division, aligning with queue mappings and agent assignments.

Proper configuration of division Ids is essential for maintaining accurate access control, consistent routing logic, and reliable integration behavior between Genesys Cloud and ServiceNow.

When you set up the Unified Experience from Genesys and ServiceNow integration, you must provide the ServiceNow Digital Messaging Token in the Credentials of the integration. The token is assigned or generated when you set the Message Auth while enabling authentication on the VA Bot Integration API. For more information, see Set up the integration for ServiceNow in Genesys Cloud and Message authentication.