Create an auth token in the ServiceNow secondary instance

task australia Updated Sep 10, 2026 1 min read create-auth-token-sn-secondary-instance.md

To use ServiceNow® Virtual Agent as a secondary bot with Virtual Agent Bot Interconnect, create an authentication token in the secondary instance.

Before you begin

Create a connection and credential in Virtual Agent Bot Interconnect.

Role required: admin

About this task

Ensure that the type of authentication (Static or Hash) and token or hash secret in the secondary instance is the same as the type and token or hash secret in the Bot Interconnect instance.

Procedure

Navigate to All, and then enter token_verification.list in the filter.
On the Token Verifications page, click New.

On the form, fill in the fields.

Field	Description
Name	A unique name for the authentication token, such as `SNSecondaryBotToken`.
Token	The static token or hash secret you provided in the Bot Interconnect (primary) instance.

Click Submit.
Navigate to All, and then enter message_auth.list in the filter.
On the Message Auth page, click New.

On the form, fill in the fields.

Field	Description
Name	Name of the message authentication, such as `SNtoSNAuthtoken`.
Provider	Name of the provider, such as `ServiceNowProvider`.
Group name	Name used to classify the provider.
Service Portal	Set this field to link users on Virtual Agent integrations such as Slack and Microsoft Teams to a service portal login page. If the field is empty, Virtual Agent redirects the users to the instance login page.
Inbound message verification	The name of the authentication token you created in the secondary instance. For example, `SNSecondaryBotToken`.
Outbound message creation	The name of the authentication token you created in the secondary instance. For example, `SNSecondaryBotToken`.
Outbound service token	The name of the authentication token you created in the secondary instance. For example, `SNSecondaryBotToken`.

Click Submit.
Navigate to All, and then enter sys_cs_provider_application.list in the filter.
Open the VA Bot to Bot Provider Application record.
In the Message auth field, select the name of the message authentication record you created.

For example, select SNtoSNAuthtoken.
Click Update.

71 lines · 3.1 KB Wrap lines

---
title: Create an auth token in the ServiceNow secondary instance
description: To use ServiceNow Virtual Agent as a secondary bot with Virtual Agent Bot Interconnect, create an authentication token in the secondary instance.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/conversational-interfaces/create-auth-token-sn-secondary-instance.html
release: australia
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Using ServiceNow Virtual Agent as a secondary bot, Virtual Agent Bot Interconnect, Conversational Interfaces]
---

# Create an auth token in the ServiceNow secondary instance

To use ServiceNow® Virtual Agent as a secondary bot with Virtual Agent Bot Interconnect, create an authentication token in the secondary instance.

## Before you begin

[Create a connection and credential in Virtual Agent Bot Interconnect](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/create-connection-credential-two-sn-instances.md).

Role required: admin

## About this task

Ensure that the type of authentication \(Static or Hash\) and token or hash secret in the secondary instance is the same as the type and token or hash secret in the Bot Interconnect instance.

## Procedure

1.  Navigate to **All**, and then enter `token_verification.list` in the filter.

2.  On the Token Verifications page, click **New**.

3.  On the form, fill in the fields.

    |Field|Description|
    |-----|-----------|
    |Name|A unique name for the authentication token, such as `SNSecondaryBotToken`.|
    |Token|The static token or hash secret you provided in the Bot Interconnect \(primary\) instance.|

4.  Click **Submit**.

5.  Navigate to **All**, and then enter `message_auth.list` in the filter.

6.  On the Message Auth page, click **New**.

7.  On the form, fill in the fields.

    |Field|Description|
    |-----|-----------|
    |Name|Name of the message authentication, such as `SNtoSNAuthtoken`.|
    |Provider|Name of the provider, such as `ServiceNowProvider`.|
    |Group name|Name used to classify the provider.|
    |Service Portal|Set this field to link users on Virtual Agent integrations such as Slack and Microsoft Teams to a service portal login page. If the field is empty, Virtual Agent redirects the users to the instance login page.|
    |Inbound message verification|The name of the authentication token you created in the secondary instance. For example, `SNSecondaryBotToken`.|
    |Outbound message creation|The name of the authentication token you created in the secondary instance. For example, `SNSecondaryBotToken`.|
    |Outbound service token|The name of the authentication token you created in the secondary instance. For example, `SNSecondaryBotToken`.|

8.  Click **Submit**.

9.  Navigate to **All**, and then enter `sys_cs_provider_application.list` in the filter.

10. Open the VA Bot to Bot Provider Application record.

11. In the **Message auth** field, select the name of the message authentication record you created.

    For example, select **SNtoSNAuthtoken**.

12. Click **Update**.