Inbound Request Configuration table

  • Release version: Yokohama
  • Updated July 20, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Inbound Request Configuration table

    The Inbound Request Configuration table (sntmtcoreinboundqueueconfig) is a metadata table that enables ServiceNow administrators to define how flows within an Inbound Request are processed and tracked. It determines whether flows execute synchronously or asynchronously, supports notification configuration, and adapts the Sales and Order Management Request Tracker across all CRM flows. This table requires the Sales and Service Core API (app-tmt-core) plugin.

    Show full answer Show less

    The existing Inbound Request table references this configuration table to track completion status and control flow execution modes.

    Key Features

    • Processing Mode Configuration: Specify whether requests run synchronously, asynchronously, or use a custom script to decide (Advanced mode).
    • Notification Settings: Configure notification types—None, Default (notifications only for asynchronous requests), or Custom notifications triggered by events.
    • Flow Tracking: Supports monitoring request completion status with different processing modes.
    • Extensibility: Allows use of the IBQConfigBase API for custom processing logic.

    Configuration Fields

    Admins create records in this table to define each flow's behavior using key fields:

    • Config ID: Unique identifier for the configuration.
    • Label: Name for the configuration record.
    • Active: Enables or disables the configuration record (default is inactive).
    • Run Mode: Sets synchronous, asynchronous, or advanced (custom scripted) processing.
    • Trigger Notification: Controls notification preferences (None, Default, Custom).
    • Configuration API: Reference to the script used for processing inbound requests.

    Security and Roles

    Access to the Inbound Request Configuration table is controlled through roles:

    • Admin: Full create, read, update, delete rights.
    • Inbound Queue Admin (sntmtcore.inboundqueueadmin): Can create, read, and update records.

    Practical Benefits for ServiceNow Customers

    This configuration framework allows customers to customize how inbound CRM and order management requests are processed and tracked, providing flexibility in synchronous vs asynchronous execution and tailored notification mechanisms. It helps streamline flow management, improve process visibility, and align notifications with business needs, all within a secure role-based access control environment.

    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

    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.

    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

    An admin creates a record in the table and specifies the configuration using the run_mode, trigger_notification, and configuration_api fields.
    Table 1. Field and descriptionsList of fields on the inbound request configuration table, their descriptions, and the type of fields.
    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.
    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.

    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.
    Configuration API Script required to process the inbound request.

    To learn more about the configuration API, see IBQConfigBase API - Scoped.

    		 Reference: sys_script_include
    Domain The current domain scope of the record, for example global. Domain ID

    Security roles

    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.
    Table 2. Roles and access
    Role Access
    Admin Create, read, update, delete
    Inbound Queue Admin (sn_tmt_core.inbound_queue_admin) Create, read, update