InServiceNow IntegrationHub, third-party API integrations within aFlow Designerflow are known asspokes. Aspokeis a scoped application containingFlow Designer actions and subflowsthat allow the flow to interact with external systems or ServiceNow applications.
Spokes in IntegrationHub
Aspokeis a collection ofpredefinedandcustomactions, subflows, and data streamsused to integrate with external systems.
Spokes provide ano-code/low-codeapproach to integrating third-party applications.
Examples ofprebuilt spokesavailable in ServiceNow include:
Slack Spoke(for Slack API integrations)
Microsoft Teams Spoke(for Teams integration)
Jira Spoke(for integrating with Atlassian Jira)
How Spokes Work
When a flow needs to interact with an external system (e.g., sending data to Jira or retrieving information from Slack), itcalls an action from a spoke.
Each spoke containsmultiple predefined actionsthat execute API requests or perform tasks like creating records, updating data, or fetching information.
Comparison with Other Options
A. an action→ Incorrect
Actions are individual steps in a flow, not the complete integration package. Actions exist inside spokes.
C. a connection→ Incorrect
Aconnectionis a configuration that stores authentication details (e.g., API keys, OAuth tokens) used by a spoke.
D. an integration step→ Incorrect
No such term as “integration step” exists in ServiceNow IntegrationHub.
ServiceNow Docs - IntegrationHub Overview:https://docs.servicenow.com/en-US/bundle/utah-integrationhub/page/integrate/integrationhub/concept/integrationhub-overview.html
ServiceNow Docs - Spokes in Flow Designer:https://docs.servicenow.com/en-US/bundle/utah-integrationhub/page/administer/integrationhub-spokes/concept/available-spokes.html
Key Concepts Related to IntegrationHub and SpokesOfficial References from the Certified System Administrator (CSA) Documentation:
Submit