IntegrationHub & Spokes

IntegrationHub is the low-code engine behind almost every integration on this list. Master the connection → credential → spoke → flow pattern once and every other system becomes a variation of it.

• admin and an IntegrationHub subscription (Starter includes REST/Flow actions; Standard/Enterprise unlock spokes).
• For on-prem targets, a running MID Server.

• Open the ServiceNow Store, find the spoke (e.g. Jira, Slack, Microsoft), and click Get.
• Spokes install their actions, a Connection & Credential alias, and sometimes example flows.

• Go to Connections & Credentials → Credentials.
• Choose the type the target needs: Basic Auth, API Key, or OAuth 2.0 (Authorization Code for user context, Client Credentials/JWT for server-to-server).
• Store secrets here, never hard-code them in a flow.

• Under Connection & Credential Aliases, open (or create) the alias the spoke uses.
• Add a Connection record: base URL of the target, the credential from Step 2, and Use MID Server if on-prem.
• The alias is the key idea, flows reference the alias, so you can swap dev/test/prod connections without editing flows.

• In Flow Designer, create a flow with a trigger (record created/updated, scheduled, or inbound).
• Add the spoke's action (e.g. Create Issue), pick the connection alias, and map inputs from the trigger.
• Use the action's outputs (IDs, status) in later steps, e.g. write a returned key back to the record.

• Add the REST step (or a Scripted REST resource for inbound) and point it at the alias.
• This covers any API without a packaged spoke.

// Outbound REST via a connection alias (flow REST step)
Method:  POST
Connection: {alias}
Resource path: /rest/api/2/issue
Headers: Content-Type: application/json
Body: { "fields": { "summary": "{{trigger.record.short_description}}" } }

• For a reusable in-house API, create a scoped app, define Flow Actions with typed inputs/outputs, and publish them as your own spoke.

• Use Flow Designer → Test and inspect Executions for each step's input/output.
• Check Outbound HTTP Requests logs for the raw call and response.
• Capture the connection, flow and actions in an update set; re-point the connection alias in each environment.