IntegrationHub Usage Table - Connect Action to Flow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2024 11:54 AM - edited 10-21-2024 11:54 AM
Is there a way to show which flow each action is triggering?
Ex. If I have a flow titled 'Test' which uses an action titled 'Connection', I would see 'Connection' as the Artifact Name and would like to see which flows, 'Test' included, are utilizing this action.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2024 12:06 PM
Hi Charis,
Usually the Flows are stored in ‘sys_flow’ and Actions in ‘sys_flow_action’ tables these can be viewed by sys_flow_action.LIST in navigation.
Navigate to the above list of Actions and add filters - Name = Connection > this gives list of Actions used in each Flow (add column labe Flow)
Note: if sysIDs are shown instead of Flow names, then you can use a Fix script to GlodeRecord(sys_flow_action) by giving addQuery(name, xyz) then GR(sys_flow) to get the Flow names.
If my response proves useful, please mark it "Accept as Solution" and "Helpful". This action benefits both the community and me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2024 12:11 PM
Hi Akash,
I'm not able to see either sys_flow or sys_flow_action table. I see sys_hub_action_type_definition as the action table and sys_hub_flow as the flow table - are these the same?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Yes
ServiceNow has changed some table names over releases (especially with Flow Designer & Workflow Studio). What you are seeing is correct for newer versions:
Flows → sys_hub_flow
(this replaces the older sys_flow)
Subflows → sys_hub_subflow
(replaces sys_subflow)
Flow actions → sys_hub_action_type_definition
(this is the definition of actions you can drag into a flow — in older versions this was sys_hub_action_type)
Spokes (integrations) → still live in sys_spoke
(sometimes you’ll also see sys_hub_spoke in older documentation, but in your instance it’s consolidated under sys_spoke)
Flow execution/runtime → sys_flow_context & sys_flow_step are still used for logs/tracking.
So in your instance:
sys_hub_flow → design-time flow definitions
sys_hub_action_type_definition → action definitions (integration steps)
sys_spoke → integrations (Slack, Jira, Teams, etc.)
If your goal is to find which integration a flow is using, you’ll need to join:
sys_hub_flow → the flow
sys_hub_action_type_definition → actions inside the flow
sys_spoke → the spoke/integration the action belongs