--- sourceDocument: Brazil Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Explore # Exploring Integration Hub {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Exploring Integration Hub ServiceNow® Integration Hub enables you to build reusable integrations with third-party systems and invoke them from anywhere within the ServiceNow AI Platform. It supports both inbound and outbound integrations, allowing you to automate workflows triggered by external events or ServiceNow events using prebuilt or custom integrations known as spokes. Integration Hub simplifies integration processes by providing tools like Workflow Studio, Spoke Generator, and the Connections dashboard. Show full answer Show less ## Inbound and Outbound Integration **Inbound integration** lets external systems trigger flows in ServiceNow via conditional, event-driven webhooks that execute workflows and update records. **Outbound integration** enables ServiceNow to execute third-party API calls as part of flows, using spokes for common applications like Slack or Microsoft Teams without scripting. ## Building and Using Integrations * **Create spokes:** Use Spoke Generator to automate tasks with reusable actions and custom integrations. * **Use base system spokes:** Quickly add actions such as posting messages to communication channels or synchronizing data across instances. * **Build custom integrations:** Develop integrations using REST or Script steps within Workflow Studio. * **Automate inbound integrations:** Define external trigger endpoints that authenticate and respond to third-party webhooks. * **Delegate administration:** Use custom actions to run processes on MID Servers, including PowerShell or REST steps. * **Import and stream data:** Utilize Integration Hub - Import for simplified, scheduled or on-demand data imports, and Stream Connect for Apache Kafka to stream data bi-directionally between ServiceNow and external systems. ## Managing Connections and Credentials Integration Hub uses **aliases** to manage credentials and connection information centrally, simplifying multi-environment and multi-account integrations. The Connections dashboard allows easy configuration, editing, and overview of connection aliases and their child connections. This supports multiple connections to the same provider (e.g., multiple Jira environments). You can override connections in flows and maintain them independently when promoting flows to production. The Personal Authentication dashboard lets users manage their own credentials for third-party integrations securely. Integration Hub supports outbound REST and SOAP calls via MID Server using mutual TLS (mTLS) authentication, with credentials and certificates stored securely. ## Benefits * Consolidates multiple automation capabilities into a single interface for building and visualizing business processes and integrations. * Extends Workflow Studio to integrate with external systems seamlessly. * Enables subject matter experts to create and share spokes, promoting collaboration between business and technical users. * Provides natural-language descriptions of integration logic to enhance understanding for non-technical users. ## Development Process Custom integrations are developed within scoped applications that group actions as spokes in Workflow Studio. Development tasks typically include creating the scoped application, publishing test versions, deploying to test instances, and verifying functionality. Once tested, spokes can be published to the application repository, ServiceNow Store, or ServiceNow Share for broader use. Branding options include adding custom icons to spokes for easier identification. 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 {#exploring-integration-hub__section_ql1_vcz_fcb} 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 {#exploring-integration-hub__section_p4b_str_tfc} 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](https://www.servicenow.com/docs/a~ztxCWaKJc5H_LIMSpi4Q "Use the Slack spoke to post messages and manage access to channels."), or [Microsoft Teams Spoke](https://www.servicenow.com/docs/LmnIr68YOCK0f7ot6akvxA "The Microsoft Teams spoke provides actions which post messages and ServiceNow incident, problem, and change record details to Microsoft Teams channels.") communications channels. * Synchronize data across multiple production instances using [Integration Hub Remote Process Sync](https://www.servicenow.com/docs/LYWjatf~wyoSkMrRcJWv4g "Integration Hub Remote Process Sync enables you to set up one-way or bidirectional integrations among multiple ServiceNow instances, so that your process flows stay in sync."). {#exploring-integration-hub__ul_t4y_qng_gcb} Create custom integrations : Build custom integrations with Workflow Studio using a [REST step](https://www.servicenow.com/docs/KRtKD0C8bXSYxWpVvOd64w "Send an outbound REST web service request to an external system.") or a [Script step](https://www.servicenow.com/docs/access?context=javascript-step-action-designer&version=brazil&pubname=brazil-build-workflows&ft:locale=en-US). Automate inbound integrations with third-party applications : [Set up a flow with external trigger definition](https://www.servicenow.com/docs/ZnFtuKvaCowIvTGvuOMK2A "Set up a flow that responds to an event-driven external trigger from a third-party system and executes.") on Workflow Studio by selecting base system external trigger definitions, and actions from the spokes or core actions. Then, [Set up external trigger endpoints](https://www.servicenow.com/docs/1ygRowMUMF9DEw4LdzvQ3A "Generate an endpoint that the external webhook in the third-party application uses to connect to your ServiceNow instance. You can deactivate or remove the configuration of the endpoint from the connection when you want the endpoint to no longer listen to the external webhook.") 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](https://www.servicenow.com/docs/access?context=mid-server-landing&version=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US) in your network. For example, actions that use the [PowerShell step](https://www.servicenow.com/docs/gMoH6BDkyUTEVQwV6pY_ug "Run PowerShell scripts on remote machines from your ServiceNow instance through a MID Server.") or [REST step](https://www.servicenow.com/docs/KRtKD0C8bXSYxWpVvOd64w "Send an outbound REST web service request to an external system."). ## Import and stream data {#exploring-integration-hub__section_lxs_15r_tfc} Import data with Integration Hub - Import. [Integration Hub - Import](https://www.servicenow.com/docs/~DGUpPzOnQoHLntPrlcyUA "Automate data import tasks through a consolidated interface that provides a guided, step-by-step experience. Define external data sources, specify target tables, map how source data becomes target data, and schedule regular imports.") 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 {#exploring-integration-hub__section_wtq_q5r_tfc} 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](https://www.servicenow.com/docs/access?context=credentials-connections-alias&version=brazil&pubname=brazil-platform-security&ft:locale=en-US). View and configure your connection and credential aliases with the [Connections dashboard](https://www.servicenow.com/docs/q~fFjwxFx0MIlh0xNZ_mmA "View and configure your connection and credential aliases through a simplified interface. Add new connections, edit existing connections, and view connection details."). 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](https://www.servicenow.com/docs/D9pGgVwvfvFrzWX3lknyWg "Support several connections to a single integration provider. Select connections for flows, subflows, and actions directly from a flow.") 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](https://www.servicenow.com/docs/_TOYv5z_nMy7_62B7Pq4wQ "Use your personal credentials to connect to third-party integrations. View, authenticate, revoke, and renew your personal authentications through a simplified, consolidated interface."). 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](https://www.servicenow.com/docs/GXqo~EUvgIRaMZbN95z10g#mtls-mid-server "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."). 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 {#exploring-integration-hub__section_fnt_m1z_fcb} 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. {#exploring-integration-hub__ul_jc5_yrg_gcb} ## Development process {#exploring-integration-hub__section_pd3_gly_fcb} 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. {#exploring-integration-hub__ul_v2z_mty_fcb} {#exploring-integration-hub__ol_sqg_jty_fcb} Review Workflow Studio design considerations in the Architecture Overview.