Development · LessonBy Neelima, ServiceNow Architect · Published · ServiceNow · all levels
IntegrationHub spokes
Use prebuilt spokes for Microsoft, Slack, Jira and more, and know what they cost and what they cannot do.
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
Practice challenge
+0 XPStreak ×0
Question 1 of 2
What holds the environment specific endpoint for a spoke?
Frequently asked questions
Can we build our own spoke?
Yes. Create a scoped application with a connection alias and a set of actions. That is exactly how the shipped spokes are built.
Do spokes work through a MID server?
Many do. The connection record can specify a MID server so the call originates inside your network.