---
sourceDocument: Australia Conversational Interfaces
sourceDocumentLink: https://www.servicenow.com/docs/r/conversational-interfaces

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Define the Virtual Agent link actions to notification content

# Define the Virtual Agent link actions to notification content {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Create the link actions for Virtual Agent notification content to be delivered in a chat or messaging channel as actionable notifications.

## Before you begin

* Ensure that you have activated the Glide Virtual Agent plugin (com.glide.cs.chatbot).  
  Note:  
  Only Virtual Agent Pro customers can associate actions with notification contents and receive actionable notifications.
* Role required: virtual_agent_admin or admin.
{#define-va-notif-link-actions__ul_g2k_csn_npb}

## About this task

Notification content, with no associated link actions, is delivered as a non-actionable notification.

## Procedure

1. Navigate to AllSystem NotificationProviderNotifications and select the notification for which you're defining the link actions.
2. In the Link Actions related list, select New.
3. On the form, fill in the fields.  
   {#define-va-notif-link-actions__table_jbc_wtb_lpb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the link action. |
   | Actions | Notification action that the link action is created to. You can select one or more notification actions for a notification and also put them in the order that you want them to be shown on the notification. |
   | Actions listed in event parm1 | Actions listed in an event parameter. Users and actions cannot both be passed into the parameter. For example, if you input a sys_id of a user in event param1, the user is considered in the output. |
   | Application | Application scope of the notification content. |
   | Notification | Notification that is associated with the content. This field is populated automatically with the notification that you created. |
   | Content | Notification content for the link action created. |
   | Active | Option to activate the notification content. |
   | Actions listed in event parm2 | Actions listed in an event parameter. Users and actions cannot both be passed into the parameter. For example, if you input a sys_id of a user in event param2, the user is considered in the output. |
   [Table 1. Actionable Content form]

   {#define-va-notif-link-actions__table_jbc_wtb_lpb}
4. Select Submit.
5. To define another link action for the notification content, repeat steps 3 and 4.  
   Note:  
   Only a single notification with active content is supported for a provider. However, if the content for the notification is not active, you can define the secondary content for the notification and make that content active.
6. **Optional:** To remove the Skip action from an actionable notification, do the following steps:
   1. Select the notification and open the Link Actions to Content related list.
   2. Select the Actionable Content and select the Disable skip option.  
      Note:  
      This option only displays when the Content Type is Virtual Agent.

## What to do next

Enable Virtual Agent notifications. For more information, see
[Enable Virtual Agent notifications](https://www.servicenow.com/docs/hYicjZqk1IgicQ6tVL_o9A "Enable Virtual Agent notifications so that your end users can receive notifications in supported Virtual Agent channels.").

*[\>]: and then