The ServiceNow® Integration Hub application extends the ServiceNow® Flow Designer workflow automation capabilities by enabling you to integrate your instance data with data in external systems. Integration Hub was enhanced and updated in the Vancouver release.

Integration Hub highlights for the Vancouver release

  • 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.

New in the Vancouver release

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 Flow Designer, through the flow execution settings.
  • Create and delete Kafka topics from within the Now 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 Flow Designer. 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.

UI changes

Trigger picker lists base system external trigger definitions
The trigger picker on Flow Designer lists the preconfigured external trigger definitions that enable you to create flows that respond to external webhooks and execute.
Note: The base system external triggers are available only when you install the Jira or GitHub app from the ServiceNow Store.
Tabs on the Connections dashboard
The tiles for the spokes on the Connections dashboard now have two tabs - Inbound and Outbound. The Inbound tab enables you to set inbound integrations by generating endpoints for external webhooks by updating preconfigured external event sources on your ServiceNow instance. The Outbound tab enables you to set outbound integrations.
Note: The Inbound tab is available only when you install the Jira or GitHub app from the ServiceNow Store.
The Inbound tab comprises base system external event sources
The Inbound tab of a spoke provides the View Details button. When you select View Details, a new page shows all base system external event sources for that spoke. Your ServiceNow instance can show base system event sources for one or more authentication types.
Note: The base system external event sources are available only when you install the Jira or GitHub app from the ServiceNow Store.

Deprecations

  • 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.

Activation information

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

Related ServiceNow applications and features

Flow DesignerWorkflow Studio
Flow Designer enables process owners to automate approvals, tasks, notifications, and record operations without having to code. You can use the Flow Designer design environment to author flows and actions and to view the results they produce.
App Engine Studio
ServiceNow® App Engine Studio (AES) is a development tool for creators of varying skill levels used to build applications that meet the immediate needs of your organization.
MID Server
The Management, Instrumentation, and Discovery (MID) Server is a Java application that runs as a Windows service or UNIX daemon on a server in your local network. The ServiceNow® MID Server enables communication and the movement of data between a ServiceNow instance and external applications, data sources, and services.
Connections and Credentials
Credentials and connection information are required to gain access to a computer or network device for ServiceNow® Discovery, ServiceNow® Service Mapping, and ServiceNow® Cloud Management, or to perform work using ServiceNow® Orchestration. When adding content to share on the ServiceNow® Developer Site or the ServiceNow® Store, you can configure connections and credentials relevant to your environment without modifying built content.