--- title: Create a Virtual Agent Bot Interconnect shell topic to call Microsoft Power Virtual Agents topics description: To access topics in the Power Virtual Agents secondary bot, you must create at least one Virtual Agent Bot Interconnect topic. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/conversational-interfaces/create-primary-va-topic-ms-pva.html release: australia topic_type: task last_updated: "2026-09-10" reading_time_minutes: 2 keywords: [Virtual Agent, Bot Interconnect, Microsoft, Power, shell, topic] breadcrumb: [Using Microsoft Power Virtual Agents as a secondary bot, Virtual Agent Bot Interconnect, Conversational Interfaces] --- # Create a Virtual Agent Bot Interconnect shell topic to call Microsoft Power Virtual Agents topics To access topics in the Power Virtual Agents secondary bot, you must create at least one Virtual Agent Bot Interconnect topic. ## Before you begin Create one or more topics in Microsoft Power Virtual Agents. [Add the Direct Line secret key to your Virtual Agent Bot Interconnect instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/add-dl-secret-key-sn-instance.md). Role required: virtual\_agent\_admin or admin ## About this task There are two ways to integrate Microsoft Power Virtual Agents topics with Bot Interconnect: - Create one Virtual Agent Bot Interconnect topic per Power Virtual Agents topic. In case of NLU topics, each Virtual Agent topic has the same name as a single Power Virtual Agents topic. For example, if you have two Power Virtual Agents topics named **order a drink** and **book a ticket**, then you would create two Virtual Agent topics also named **order a drink** and **book a ticket**. In case of LLM topics, each Bot Interconnect topic has the same name and description as the corresponding Power Virtual Agents topic. - Map multiple Power Virtual Agents topics to a single Virtual Agent Bot Interconnect topic. This scenario is applicable only for NLU topics. Create one Virtual Agent topic for your Power Virtual Agents topics and name it accordingly. For example, **PVA ordering issues**. In this scenario, the Power Virtual Agents topics are mapped to the topic as either keywords or utterances, depending on your method of topic discovery. So if you have two Power Virtual Agents topics named **order a drink** and **book a ticket**, you would add both phrases to the topic as keywords or you would add them as utterances to the topic's corresponding intent. ## Procedure 1. Navigate to **All** > **Conversational Interfaces** > **Assistat Designer**. 2. Select the **Asset library** tab. 3. In the Asset library, [Create a topic](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/virtual-agent/create-virtual-agent-topic.md) for your Power Virtual Agents topics. In case of NLU topics, include the Power Virtual Agents topic names as either keywords or utterances in the corresponding ServiceNow Virtual Agent intent. In case of LLM topics, the topic name and description of the Bot Interconnect topic should match the topic name and description of the Power Virtual Agents topic. 4. On the **Flow** tab, drag a Topic Block utility node onto the canvas. 5. Select the node, and then fill in the form as follows:
Property Description
Topic Block Select **Bot Interconnect** topic block for NLU topics and **Bot Interconnect - LLM** topic block for LLM topics.
Action Name Enter: `sn_va_bot_ic.direct_line_bot_interconnect_integration_handler`
Action Type Enter `subflow`.
Additional Params \(String\) Follow these steps:1. Select the script icon \[Omitted image "icon-script.png"\] Alt text: Script icon.. 2. In the Additional Params \(String\) window, add this code: ``` (function execute() { return JSON.stringify({'quick': false}); })() ``` 3. Select **Save**.
6. Select **Save**. 7. Select **Publish**. ## What to do next Test your configuration. You can execute the topics that are available in the secondary bot from channels where Bot Interconnect is deployed. **Note:** Conversations always remain open in Power Virtual Agents.