Combined Integration Hub release notes for upgrades from Vancouver to Washington DC

  • Release version: Yokohama
  • Updated January 30, 2026
  • 8 minutes to read

    • Consolidated page of all release notes for Integration Hub from Vancouver to Washington DC.

    How to use this page

    To help you prepare for your upgrade, we have combined the cross-family Integration Hub release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Vancouver to Washington DC.

    Tip:
    If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release."

    Important information for upgrading Integration Hub to Washington DC

    Before you upgrade to Washington DC, review these pre- and post-upgrade tasks and complete the tasks as needed.

    Release Release notes

    Vancouver

    		 No updates for this release.

    Washington DC

    		 No updates for this release.

    New features

    Between your current release family and Washington DC, new features were introduced for Integration Hub.

    Release Release notes

    Vancouver
    Integration Hub - Import Enhancements
    • Map source data to multiple target tables in a single integration.
    • Configure transform settings for your data mapping. Specify batch size and empty-field handling, enable verbose mode, or run a script before or after the integration.
    • When configuring a data source, select an Excel sheet from a drop-down list instead of having to enter a sheet number.
    • View which target fields a source field has been mapped to with the check mark indicator. The check mark indicator appears next to source fields that have been mapped to a target field. Moving your cursor to the check mark displays the target fields that the source field has been mapped to, up to five fields.
    Stream Connect for Apache Kafka Enhancements
    • Configure the relative weight for Stream Connect consumers. The relative weight specifies how much processing time a consumer gets compared to other consumers. You can configure the relative weight when you create a Kafka stream or, when using , through the flow execution settings.
    • Create and delete Kafka topics from within the ServiceNow AI Platform. Creating a topic adds it to both the Kafka Topics [sys_kafka_topic] table and to Hermes. Deleting a topic removes it from both the Kafka Topics [sys_kafka_topic] table and from Hermes.
    Set up a flow
    Create flows that respond to external webhooks or triggers and execute by selecting base system external trigger definitions from the trigger picker and then actions from the action picker in . When you execute the appropriate external webhook from a third-party application, your ServiceNow instance authenticates it and the flow that set executes.
    Note:
    The base system external trigger definitions are available only when you install the Jira or GitHub app from the ServiceNow Store.
    Set up external trigger endpoints
    Generate endpoints that enable you to configure external webhooks on third-party systems. Generate the endpoints by updating the base system external event sources on your ServiceNow instance. After that, you can configure the endpoint on the third-party application and enable it to send a webhook to the ServiceNow instance to execute a flow. Based on the authentication type that the third-party system supports, you can generate a hash or token, or add roles to the external event source. Finally, you generate the endpoint that you can use on the third-party system webhook.
    Note:
    The base system external event sources are available only when you install the Jira or GitHub app from the ServiceNow Store.
    OpenAPI step
    Import the OpenAPI specification of an external outbound REST web service and make REST requests to the web service.
    Retrieve connection information in a Data Stream action
    Retrieve connection and credential details to use in your Data Stream action. This option is available in the Action Preprocessing section of the Data Stream action. When selected, it adds the Get Connection Info step as the first step in the action preprocessing for the Data Stream action.
    Create a JSON payload with the JSON Builder step

    Create a JSON payload to use in another step. Enter values or use data pills to produce a dynamic payload. This step supports several data types, including objects and arrays for nested structures.

    Format time and currency values for data exports with Excel
    • Format duration fields in days, hours, and minutes, instead of just seconds, with the glide.export.excel.duration.readable_string property. When true, duration field values are formatted in days, hours, and minutes. For example, an Actual elapsed time field might have a value of 2 days, 5 hours, and 16 minutes. When false, duration field values are formatted in seconds. For example, the same Actual elapsed time field would have a value of 191,760 seconds.
    • Format currency values to match the localization of the instance with the glide.excel.local_based_currency property. When true, currency value formats match the localization of the instance. For example, on an instance using Canadian French, a currency value of 6300 would be correctly formatted as 6,300 €. When false, the same value is formatted as € 6,300.

    Washington DC
    Stream Connect for Apache Kafka Enhancements
    • Use Stream Connect Message Replication to replicate data between your local Apache Kafka environment and ServiceNow. With Stream Connect Message Replication, you no longer need a third-party replicator and can manage message replications from your ServiceNow instance.
    • Use Stream Connect Message Replication to enable a MID Server to create the access certificates required to connect to the Hermes Messaging Service. The MID Server can automatically generate the necessary certificates, so you don't need to configure them manually.
    • Send messages with an updated Kafka Producer step. Select a topic from a drop-down list and configure values for the message header.
    OAuth 2.0 credentials
    Connect with an on-premise third-party OAuth authorization server that resides behind a firewall through a MID Server that sends the request for an OAuth token on behalf of your ServiceNow instance. You can use this functionality when you create an application registry for a third-party OAuth provider and in the form, set the Grant type as Client Credentials.
    Increased security in code signing with multi-layer caller inspection
    The code signing feature has been enhanced with multi-layer caller inspection of records. Multiple layers can call each other before a record or entity can update the ECC queue table. Now, each layer must have a valid certificate and validated before the MID server accesses the record or entity. The ServiceNow platform provides a property that enables you to inspect three caller layers by default.

    Changes

    Between your current release family and Washington DC, some changes were made to existing Integration Hub features.

    Release Release notes

    Vancouver

    		 No updates for this release.

    Washington DC
    Open API step enhancements
    The OpenAPI step has several improvements. You can now:
    • Save the request response as an attachment record.
    • Configure a retry policy to retry a request if the previous one fails or encounters any issues.
    • Sync step inputs and step outputs with action inputs and action outputs. Edit step outputs if required.
    • Modify the resource path, HTTP methods, query parameters, and headers of a request.
    • Add or remove error mapping to an action while resetting action inputs and action outputs.
    • Use oneOf and anyOf schema object properties in the schema.
    Multi-layer caller inspection of records going to the ECC queue
    Previously, there would be a single layer inspection of records or entities entering the ECC queue. Now, multiple layers calling each other must have a valid certificate and be validated before the record enters the ECC queue. By default, you can support the inspection of three layers.

    Removed

    Between your current release family and Washington DC, some Integration Hub features or functionality were removed.

    Release Release notes

    Vancouver

    		 No updates for this release.

    Washington DC

    		 No updates for this release.

    Deprecations

    Between your current release family and Washington DC, some Integration Hub features or functionality were deprecated.

    Release Release notes

    Vancouver
    • The JSON portion of the Payload Builder step is deprecated and replaced by the JSON Builder step.
    • Starting with the Vancouver release, Microsoft Active Directory Spoke is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported. Microsoft Active Directory v2 Spoke provides the latest experience for this functionality. For details, see the Deprecation Process [KB0867184] article in the Now Support knowledge base.

    Washington DC

    Starting with Washington DC release, OpenAPI support in the REST step is being prepared for future deprecation. It will be hidden and no longer available for activation but will continue to be supported. For details, see the Deprecation Process [KB0867184] article in the Now Support Knowledge Base.

    Activation information

    Review information on how to activate Integration Hub.

    Release Release notes

    Vancouver

    Integration Hub is included in and is available with activation of an subscription package. For details, see https://www.servicenow.com/products/automation-engine.html.

    Washington DC

    Integration Hub is included in and is available with activation of an subscription package. For details, see https://www.servicenow.com/products/automation-engine.html.

    Additional requirements

    If any additional requirements were introduced or changed for Integration Hub we have noted them here.

    Release Release notes

    Vancouver

    		 No updates for this release.

    Washington DC

    		 No updates for this release.

    Browser requirements

    If any specific browser requirements were introduced or changed for Integration Hub we have noted them here.

    Release Release notes

    Vancouver

    		 No updates for this release.

    Washington DC

    		 No updates for this release.

    Accessibility information

    Review details on accessibility information for Integration Hub, such as specific requirements or compliance levels.

    Release Release notes

    Vancouver

    		 No updates for this release.

    Washington DC

    		 No updates for this release.

    Localization information

    If there are specific localization considerations for Integration Hub we have noted them here.

    Release Release notes

    Vancouver

    		 No updates for this release.

    Washington DC

    		 No updates for this release.

    Highlight information

    If there are specific highlight considerations for Integration Hub we have noted them here.

    Release Release notes

    Vancouver
    • Streamline your Integration Hub - Import integrations by mapping source data to multiple target tables in a single integration.
    • Specify how much processing time each Kafka consumer gets, relative to the others, by configuring each consumer's relative weight.
    • Build JSON payloads with complex data types and nested structures.

    See Integration Hub for more information.

    Washington DC
    • Simplify your Stream Connect integrations by using Stream Connect message replication to replicate data from your local Apache Kafka environment.
    • Use the improved OpenAPI step for integrating with third-party REST web services.
    • Authenticate the OAuth client credential grant type with the on-premise authorization server, and integrate with the corresponding resource server after successful authentication.
    • Use the code signing feature that has been enhanced with multi-layer caller inspection of records in the call stack to be signed before going to the ECC queue.

    See Integration Hub for more information.