IntegrationHub spokes
Quick answer
Use prebuilt spokes for Microsoft, Slack, Jira and more, and know what they cost and what they cannot do.
Key takeaways
- Spokes trade custom code for licensed, supported actions
- Connection and credential aliases keep environments separate
- Check the licensing tier before committing to a spoke
- A single REST action is sometimes the pragmatic choice
What a spoke is
A spoke is a packaged set of Flow Designer actions for one external product, with authentication handled by a connection and credential alias. Instead of writing REST calls, you drag a Post a Message action into a flow and fill in the fields.
Connections and credentials
Every spoke uses a connection alias that points at an environment specific connection record and a credential. That structure is what makes the same flow work in dev, test and production without editing the flow.
Licensing and limits
IntegrationHub is licensed by transaction volume and tier.
- Check which tier a spoke needs before designing around it
- Transactions are counted per outbound action execution
- A custom REST action can be cheaper than a premium spoke for one simple call
- Spokes update with the store, so pin a version if a flow depends on current behaviour
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
What holds the environment specific endpoint for a spoke?
- A. The flow
- B. The connection and credential alias
- C. The action script
- D. A system property
Show answer
B. The connection and credential alias
Aliases resolve to different connection records per environment.
IntegrationHub is licensed by
- A. Number of users
- B. Outbound transaction volume and tier
- C. Number of flows
- D. Instance size
Show answer
B. Outbound transaction volume and tier
Entitlement is based on transactions and the tier of the actions used.