---
sourceDocument: Yokohama Customer Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/customer-service-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Customer Service Management

ft:clusterId :

    - csm

bundleId :

    - csm

workflow :

    - Customer and Industry


---

# Inbound Request Configuration table

# Inbound Request Configuration table {#ariaid-title1}

Release version: Yokohama  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
The Inbound Request Configuration table enables users to define the configurations to determine how each flow is processed and tracked within an Inbound Request.

## Overview of the Inbound Request Configuration table {#inbound-request-configuration-table__section_o15_xrv_1fc}

The Sales and Service Core API (app-tmt-core) plugin is required to use the Inbound Request Configuration table (sn_tmt_core_inbound_queue_config).

The Inbound Request Configuration table is a metadata table that must be configured to decide how a particular flow is executed, whether synchronous or asynchronous.  
The table can be used to perform the following tasks.

* Enable admins to configure synchronous vs asynchronous processing of requests.
* Adapt the Sales and Order Management Request Tracker across all CRM flows.
* Enable configuration of notification types, whether default, custom, or no notifications.
{#inbound-request-configuration-table__ul_rcn_psv_1fc}

The Request Configuration field on the existing Inbound Request Table \[sn_tmt_core_inbound_queue\] is a reference to the new Inbound Request Configuration table (sn_tmt_core_inbound_queue_config).

Any workflow that requires the tracking of a completion status, can use the Inbound Request Configuration table and configure whether a flow is synchronous or asynchronous.

## Fields on the Inbound Request Configuration Table {#inbound-request-configuration-table__section_i2h_ktv_1fc}

An admin creates a record in the table and specifies the configuration using the run_mode, trigger_notification, and configuration_api fields.{#inbound-request-configuration-table__table_f3d_3tv_1fc__entry__3}

| Field | Description | Type |
|-|-|-|
| Config ID | Unique configuration ID for the metadata configuration. | String |
| Label | Unique label name for the metadata configuration. | Translated text |
| Active | Specifies whether the Inbound request configuration record is active or not. | True/False Default value is False |
| Run Mode | Specifies whether a request runs synchronously or asynchronously. | String (choices): Sync, Async, Advanced. * Synchronous: Synchronous processing. * Asynchronous: Asynchronous processing * Advanced: Use custom script to determine if the flow has to be synchronous or asynchronous. {#inbound-request-configuration-table__ul_at4_s5v_1fc} |
| Trigger Notification | Specifies how a user wants to receive notifications. A notification is triggered in one of the following situations. * Trigger notification field is set to Default. * State of a request is Complete and the status is either Success or Partial success. {#inbound-request-configuration-table__ul_rvv_y5v_1fc} The notifications for the record in the Inbound table are only received by whoever has initiated the flow. | String (choices): None, Default, Custom * None: No notifications * Default: Notifications only for asynchronous requests. * Custom: Custom notification for asynchronous requests based on requirements.Configure custom notifications by using the existing event (sn_tmt_core.ibq.custom.notification) or by handling your own custom event. Default value for the field is Default. {#inbound-request-configuration-table__ul_dbl_3vv_1fc} |
| Configuration API | Script required to process the inbound request. To learn more about the configuration API, see [IBQConfigBase API - Scoped](https://www.servicenow.com/docs/access?context=IBQConfigBaseAPIBoth&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US). | Reference: sys_script_include |
| Domain | The current domain scope of the record, for example global. | Domain ID |
[Table 1. Field and descriptionsList of fields on the inbound request configuration table, their descriptions, and the type of fields.]

{#inbound-request-configuration-table__table_f3d_3tv_1fc}

## Security roles {#inbound-request-configuration-table__section_tzz_bwv_1fc}

The security roles for the Inbound Request Configuration table (sn_tmt_core_inbound_queue_config) provide different levels of access to the \[sn_tmt_core.inbound_queue_admin\] role.{#inbound-request-configuration-table__table_mhz_2wv_1fc__entry__2}

| Role | Access |
|-|-|
| Admin | Create, read, update, delete |
| Inbound Queue Admin (sn_tmt_core.inbound_queue_admin) | Create, read, update |
[Table 2. Roles and access]

{#inbound-request-configuration-table__table_mhz_2wv_1fc}
**Related topics**   

* [IBQConfigBase API - Scoped](https://www.servicenow.com/docs/access?context=IBQConfigBaseAPIBoth&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US)