Exploring Integration Hub

ServiceNow® Integration Hub enables you to build reusable integrations with third-party systems and call them from anywhere in the ServiceNow AI Platform. For example, you can request Integration Hub to call external systems using integration APIs from the Action Designer Script step, run the Script step on the ServiceNow® MID Server, and activate protocol steps like REST, SOAP, and PowerShell.

Inbound and outbound integration

The Integration Hub provides both inbound and outbound integration with third-party applications.

Inbound integration occurs when a flow that you set up on Workflow Studio responds to a conditional and event-driven external webhook from a third-party system and executes. For example, when you create a P1 issue on an issue-tracking application, its external webhook triggers a flow in the ServiceNow instance and an incidence database table is updated in the ServiceNow instance. Here, the webhook is conditional and event-driven.

Outbound integration occurs when the Integration Hub enables execution of third-party APIs as a part of a flow when a specific event occurs in ServiceNow. These integrations, referred to as spokes, are easy to configure and enable you to quickly add powerful actions without the need to write a script. For example, you can post a message and incident details in a Slack channel when a high priority incident is created.

Building integrations

Build reusable integrations with third-party systems and call them from anywhere in the ServiceNow AI Platform.

Create spokes

Build spokes using Spoke Generator to automate integration tasks by creating a sequence of reusable actions to develop custom integrations. For more information, see .

Use spokes for base system integrations

Using Integration Hub actions in Workflow Studio, you can:

• Post messages and ServiceNow incident, problem, and change record details to Slack Spoke, or Microsoft Teams Spoke communications channels.
• Synchronize data across multiple production instances using Integration Hub Remote Process Sync.

Create custom integrations

Build custom integrations with Workflow Studio using a REST step or a Script step.

Automate inbound integrations with third-party applications

Set up a flow with external trigger definition on Workflow Studio by selecting base system external trigger definitions, and actions from the spokes or core actions. Then, Set up external trigger endpoints that the third-party application webhooks use to trigger the flow you had set up. Your ServiceNow instance authenticates the webhook before it triggers the flow.

Automate the administration of servers and applications in your network

Use custom actions to delegate Workflow Studio processes to a MID Server in your network. For example, actions that use the PowerShell step or REST step.

Import and stream data

Import data with Integration Hub - Import. Integration Hub - Import enables you to configure, run, and schedule your data imports all through a single simplified interface. It consolidates multiple data integration capabilities into a single environment, eliminating the need to create and manage several forms throughout the platform. Its step-by-step experience guides you through the configuration of data sources, target tables, and data mapping. You can schedule your data imports or run them on demand.

Stream data with Stream Connect for Apache Kafka. Stream Connect links your Kafka environment to your ServiceNow® instance, enabling you to stream data between your instance and your external systems. Stream Connect is integrated with Workflow Studio, so you can build flows that produce and consume Kafka events. Stream Connect also provides several consumers that enable you to stream and process data with scripts or by using your existing RTE or transform map configurations.

Manage connections

Integration Hub takes advantage of aliases to manage connection information and credentials when integrating with external systems. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. Integration Hub only requires an alias, which then resolves to use the correct credentials and connection information during runtime. Learn more about credentials, connections, and aliases.

View and configure your connection and credential aliases with the Connections dashboard. The Connections dashboard enables you to manage multiple connections through a single interface, and provides simplified processes for adding, editing, and configuring connections. With the Connections dashboard, you can view details about an alias and all associated child connections in a single location.

Integration Hub supports multiple connections to a single integration provider. For example, you can have connections to several different Jira environments. In Workflow Studio, you can select which connection you want to use in a flow, and override preset connections for flows, subflows, and actions. When a flow is promoted to production, you can reestablish a connection to each account without needing to modify the flow.

Use your personal credentials to connect to third-party integrations with the Personal Authentication dashboard. View, authenticate, revoke, and renew your personal authentications through a simplified, consolidated interface.

Make outbound REST and SOAP calls through a MID Server using mTLS. Store mTLS credential and certificate information on the instance, in a configuration file, or in an external vault. The MID Server retrieves the credential and certificate information and makes outbound REST and SOAP calls using the mTLS protocol.

Benefits

Integration Hub provides process owners and developers these benefits.

• Consolidates multiple ServiceNow AI Platform automation capabilities into a single environment so process owners and developers can build and visualize business processes and integrations from a single interface.
• Extends Workflow Studio content to integrate business processes with external systems.
• Promotes business process automation by enabling subject matter experts to develop and share spokes with flow designers.
• Provides natural-language-descriptions of integration logic to help non-technical users understand triggers, actions, inputs, and outputs.

Development process

When developing a custom integration, develop all actions for the integration within a scoped application. When deployed to a target instance, these actions are grouped as a spoke in Workflow Studio. Brand the spoke by adding a custom icon to the application record. To learn more about application development, see Build applications.

When developing spokes, flow and action designers typically perform these application development tasks.

1. Create a scoped application on a development instance to build spokes.
2. Publish a test version of the scoped application to the application repository.
3. Deploy the scoped application to a test instance from the application repository.
4. Test the scoped application on the test instance.
5. When working as expected, publish the scoped application in one of the following ways.
   • Publish to the application repository for deployment on production instances.
   • Publish to the ServiceNow Store as an application that customers can request for their environments.
   • Publish to ServiceNow Share to provide content to other customers in the ServiceNow community.

Review Workflow Studio design considerations in the Architecture Overview.