Skip to main content
7.0 Duplicate

Sort/group HTTP Actions by Connector

Related products:Agent Studio
  • December 17, 2025
  • 3 replies
  • 25 views

Forum|alt.badge.img+2

hey all, was looking through my HTTP actions that i’ve created in the Agent Studio console today trying to find one i created and kept missing it and thought, it would be nice to organize or group these by connector.

for example if i have 4 actions that are using my MS Graph connector, and 6 that are using a ServiceNow connector, it would be cool to either filter the list of all HTTP actions for only the actions that match that defined connector OR even develop a view that just separates the actions visually and groups them together by sibling connector.

i have a naming scheme for my actions that i follow and it is nice that the most recently edited/used action shows at the top most of the time, but this i think would possibly be a little bit of a cleaner way to look through my ever growing list of HTTP actions.

cheers!

3 replies

Forum|alt.badge.img
  • Community Manager
  • January 20, 2026
Updated idea status1. New7.0 Duplicate
Idea merged into:

All the votes from this idea have been transferred.

Forum|alt.badge.img
  • Community Manager
  • January 20, 2026

@chaney.zimmerman thanks for the suggestion. We’ve merged this idea into our broader RBAC / Governance roadmap item (Sharing & Permissions), which is planned to introduce folders and scoped access controls.

With folders/organization in place, you’ll be able to structure assets (including HTTP Actions) in a way that aligns to connector/domain boundaries (e.g., MS Graph vs. ServiceNow), which should address the “group by connector / filter by connector” workflow you described. Hope this helps!


Forum|alt.badge.img+2

great! thanks for the information and update ​@dhorvath !