---
title: Configure Slack modals in ServiceNow instance
description: Create modal and specify fields that should be displayed in your Slack modal. Modal UI can be generated in two ways; automatically using a ServiceNow table and manually using a custom View Payload.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/integrate-applications/integration-hub/conf-slack-modals.html
release: australia
product: Integration Hub
classification: integration-hub
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 6
breadcrumb: [Slack Spoke, Integration Hub spokes, Build integrations, Integration Hub, Workflow Data Fabric]
---

# Configure Slack modals in ServiceNow instance

Create modal and specify fields that should be displayed in your Slack modal. Modal UI can be generated in two ways; automatically using a ServiceNow table and manually using a custom **View Payload**.

## Before you begin

Role required: admin.

## About this task

For example, if you want to create incident using modal in Slack, the Create Incident modal requires **Priority**, **Category**, and **Short Description** fields.

**Note:** Modals can be triggered from these interactive Slack components:

-   Command,
-   Block action,
-   Global shortcut, and
-   Message shortcut.

## Procedure

1.  To create a modal with UI that is automatically generated using a ServiceNow table:

    1.  Navigate to **Slack** > **Slack Modal Configuration**.

    2.  Click **New**.

    3.  On the Slack Modal Configuration form, fill these values.

<table id="table_fng_zsd_fpb"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Name

</td><td>

Name to identify the record. For example, `Modal to create incident`.

</td></tr><tr><td>

Modal Title

</td><td>

Modal title that is displayed on Slack. For example, `Create Incident`.

</td></tr><tr><td>

Table

</td><td>

ServiceNow table corresponding to the modal fields. For example, **Incident \[incident\]**.

</td></tr><tr><td>

Custom Modal

</td><td>

Option to configure a custom modal.

</td></tr><tr><td>

Input Fields

</td><td>

Inputs fields that should be displayed on Slack. For example, select **Priority**, **Category**, and **Short Description**. Ensure that these modal fields correspond to the selected ServiceNow table. For example, you can't display task related fields on a modal that creates an incident.**Note:** Only the string, date, and choice field types are supported.

</td></tr><tr><td>

Active

</td><td>

Option to actively use the record.

</td></tr><tr><td>

Script Validation

</td><td>

Script to validate inputs provided by the user in the modal. To validate the user-provided inputs, ensure that you are aware of the format in which values are retrieved from the modal and parse the response from Slack.The sample payload when user provides values for the **Priority**, **Category**, and **Short Description** fields in the Create Incident modal is:

```
{"priority":{"4gk":{"type":"static_select","selected_option":{"text":{"type":"plain_text","text":"1 - Critical","emoji":true},"value":"1"}}},"category":{"iV7":{"type":"static_select","selected_option":{"text":{"type":"plain_text","text":"Software","emoji":true},"value":"software"}}},"short_description":{"XS/Q=":{"type":"plain_text_input","value":"hemanth"}}}
```

 To display validation errors in the modal, configure the script to return an object keys, status, and errorObject. errorObject should have a value of object that will be displayed on Slack. The object should have response\_action and error.

 Also, configure the script to return an object with keys of status and statusMessage when there are no validation errors. statusMessage is optional and you can configure it as per your requirement.

 \[Omitted image "slack-script-validation.png"\] Alt text: Script validation.

</td></tr></tbody>
</table>    4.  Right-click the form header and click **Save**.

        The Create Incident modal is created in Slack.

        \[Omitted image "slack-modal.png"\] Alt text: Slack modal.

2.  To create a modal with UI that is manually generated using a custom **View Payload**:

    1.  Navigate to **Slack** &gt; **Slack Modal Configuration**.

    2.  Click **New**.

    3.  On the Slack Modal Configuration form, fill these values.

<table id="table_nwf_ng5_fpb"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Name

</td><td>

Name to identify the record. For example, `Modal to create incident`.

</td></tr><tr><td>

Custom Modal

</td><td>

Option to configure a custom modal. Select this check box.

</td></tr><tr><td>

View Payload

</td><td>

Payload generated by Slack Block Kit Builder that defines the modal UI. For more information, see [Block Kit](https://api.slack.com/block-kit) and [Building with Block Kit](https://api.slack.com/block-kit/building).

</td></tr><tr><td>

Active

</td><td>

Option to actively use the record.

</td></tr><tr><td>

Script Validation

</td><td>

Script to validate inputs provided by the user in the modal. To validate the user-provided inputs, ensure that you are aware of the format in which values are retrieved from the modal and parse the response from Slack.The sample payload when user provides values for the **Priority**, **Category**, and **Short Description** fields in the Create Incident modal is:

```
{"priority":{"4gk":{"type":"static_select","selected_option":{"text":{"type":"plain_text","text":"1 - Critical","emoji":true},"value":"1"}}},"category":{"iV7":{"type":"static_select","selected_option":{"text":{"type":"plain_text","text":"Software","emoji":true},"value":"software"}}},"short_description":{"XS/Q=":{"type":"plain_text_input","value":"hemanth"}}}
```

 To display validation errors in the modal, configure the script to return an object keys, status, and errorObject. errorObject should have a value of object that will be displayed on Slack. The object should have response\_action and error.

 Also, configure the script to return an object with keys of status and statusMessage when there are no validation errors. statusMessage is optional and you can configure it as per your requirement.

 \[Omitted image "slack-script-validation.png"\] Alt text: Script validation.

</td></tr></tbody>
</table>    4.  Right-click the form header and click **Save**.

        The Create Incident modal is created in Slack.

3.  Specify conditions to define when the modals should be displayed:

    1.  Navigate to **Slack** &gt; **Inbound Decisions For Modals** .

    2.  On the Decision form, fill these values.

        |Field|Description|
        |-----|-----------|
        |Label|Name to identify the inbound modal decision.|
        |Answer|Modal that must be displayed when the specified conditions are met. Ensure that you select the required record from the Slack Modal Configuration \[sn\_slack\_ah\_v2\_slack\_modal\_configuration\] table.|
        |Default Answer|Option to specify if this is the default modal. The default modal is applicable when the conditions are not met.|
        |Condition|Conditions to be met in your Slack application to display the modal.|

        **Note:**

        -   Copy and record the value of sys\_id. You can use this sys\_id as the unique value in **Callback ID** while configuring the shortcut or message shortcut in your Slack app.

            \[Omitted image "modal-slack-sysid-shortcut.png"\] Alt text: sys\_id of the modal's inbound policy record.

            **Note:** Two system properties are added to handle the inbound communications:

<table id="table_nz4_4fr_qwb"><thead><tr><th>

Category

</th><th>

Property name

</th><th>

Description

</th><th>

Example

</th></tr></thead><tbody><tr><td>

Slash commands

</td><td>

sn\_slack\_ah\_v2.command.special\_characters

</td><td>

The characters encoded using the encodeURIComponent method are handled internally. To replace any additional special characters used in Slash commands in the Slack application with their encoded URI characters, add the characters in a JSON format.

</td><td>

\{

 "~" : "%7E",

 "\\\(" : "%28",

 \}

</td></tr><tr><td>

Interactivity &amp; Shortcuts:

</td><td>

sn\_slack\_ah\_v2.interactivity.special\_characters

</td><td>

The characters encoded using encodeURIComponent method and the following characters are handled internally: `!, ', (, ), *, ~`

 Fill in the property to replace any additional special characters used in Slack Interactivity &amp; Shortcuts in the Slack application with their Encoded URI characters in a JSON format.

</td><td>

\{

 "~" : "%7E",

 "\\\(" : "%28",

 \}

</td></tr></tbody>
</table>            To display modals for the required shortcut, in **Condition**, provide the sys\_id of the modal's inbound policy record.

            \[Omitted image "slack-modal-sysid.png"\] Alt text: Display modals for Slack shortcuts.

        -   To display modals for the required Slack commands, in **Condition**, provide the required command for which the modal should be displayed.

            \[Omitted image "slack-modal-cmd.png"\] Alt text: Display modals for Slack commands.

        -   To display modals for the required Slack block action, in **Condition**, provide the required action ID of the required block action for which the modal should be displayed.

            \[Omitted image "slack-modal-actionid.png"\] Alt text: Display modals for Slack block actions.

    3.  Click **Submit**.

        When events in Slack meet conditions specified in the policy, the associated modal is displayed.

        **Note:** These inbound decisions are saved in the Decision tables. Users are cautioned against directly updating or modifying data in these tables.

4.  Specify tasks to be performed when user provides values in the modals by creating an inbound policy:

    1.  Navigate to **Slack** &gt; **Inbound Decisions**.

    2.  Click **New**.

    3.  On the Decision form, fill these values.

<table id="table_khv_ww4_3mb"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Label

</td><td>

Name to identify the inbound decision.

</td></tr><tr><td>

Answer

</td><td>

Subflow that must be triggered when the specified conditions are met.

</td></tr><tr><td>

Default Answer

</td><td>

Option to specify if this is the default answer. The default answer is applicable when the conditions are not met.1.  Click the lookup icon \(\[Omitted image "SearchIcon.png"\] Alt text: Lookup icon\).
2.  Select the required subflow from the Document list.

**Note:** Ensure that the **Table name** is `Flow [sys_hub_flow]`.

Ensure that you have configured the subflow to process the response payload from Slack to automate tasks.

</td></tr><tr><td>

Condition

</td><td>

Conditions to be met to perform tasks in ServiceNow instance. Specify the modal record in the condition.

\[Omitted image "slack-modal-subflow.png"\] Alt text: Condition to trigger subflow.

**Note:** **Condition** must have condition specific to the modal record only.

</td></tr></tbody>
</table>    4.  Click **Submit**.

        When Slack user provides inputs in the modal, the associated subflow is triggered after validating the inputs. Depending on the automations configured in your subflow, tasks are performed.