Skip to main content
Solved

Crawl workspaces on Flow for used connections

bobw
Contributor
Forum|alt.badge.img+5
  • bobwContributor
  • Contributor

Our Flow instance has more web connections than it should.  That’s the result of allowing new connections without peer review.
Now, one of our team members is leaving and I’m concerned his workspaces will use connections that won’t transfer.  (We use Entra)
Is there a way to find all the connections used in various workspaces (scheduled and on-demand apps).  I don’t see a view for that in the individual workspaces, or I’d step through them all.

Other than downloading and opening each workspace (~100), or deleting the connections to see what happens, is there a way?

Best answer by takashi

Hi ​@bobw ,

You can get the information of all repositories, workspaces, and user parameters by performing these three FME Flow REST APIs sequentially.

  1. GET /repositories
  2. GET /repositories/{repository}/items
  3. GET /repositories/{repository}/items/{item}/parameters

Since the information of each user parameter includes its name, description, type, and default value if exists, after retrieving the information of parameters with the REST APIs, you can extract every user parameter whose type is named web connection and its default value.

See also the attached workspace example to learn more. The workspace requires these parameters.

  • FME Flow Host : enter the URL of your FME Flow host
  • FME Flow Token : enter a token (with appropriate privileges) of your FME Flow

Hope this helps.

View original
Did this help you find an answer to your question?

6 replies

takashi
Influencer
  • takashiInfluencer
  • Best Answer
  • April 26, 2025

Hi ​@bobw ,

You can get the information of all repositories, workspaces, and user parameters by performing these three FME Flow REST APIs sequentially.

  1. GET /repositories
  2. GET /repositories/{repository}/items
  3. GET /repositories/{repository}/items/{item}/parameters

Since the information of each user parameter includes its name, description, type, and default value if exists, after retrieving the information of parameters with the REST APIs, you can extract every user parameter whose type is named web connection and its default value.

See also the attached workspace example to learn more. The workspace requires these parameters.

  • FME Flow Host : enter the URL of your FME Flow host
  • FME Flow Token : enter a token (with appropriate privileges) of your FME Flow

Hope this helps.

1 Attachments
david_r
virtualcitymatt
hkingsbury
4 people upvoted this
  • david_r
    david_r
  • virtualcitymatt
    virtualcitymatt
  • hkingsbury
    hkingsbury
  • bobw
    bobw
virtualcitymatt
Celebrity
Forum|alt.badge.img+35
takashi wrote:

Hi ​@bobw ,

You can get the information of all repositories, workspaces, and user parameters by performing these three FME Flow REST APIs sequentially.

  1. GET /repositories
  2. GET /repositories/{repository}/items
  3. GET /repositories/{repository}/items/{item}/parameters

Since the information of each user parameter includes its name, description, type, and default value if exists, after retrieving the information of parameters with the REST APIs, you can extract every user parameter whose type is named web connection and its default value.

See also the attached workspace example to learn more. The workspace requires these parameters.

  • FME Flow Host : enter the URL of your FME Flow host
  • FME Flow Token : enter a token (with appropriate privileges) of your FME Flow

Hope this helps.

Its too bad there no heart emoji to react to this excellent answer 

todd_davis
Influencer
Forum|alt.badge.img+22
  • todd_davisInfluencer
  • Influencer
  • April 28, 2025

I have a process that does all of this...looks at workspaces, automations, schedules, tokens, plus on and on. One of the outcomes is exactly what you are talking about, finding every location where something is referenced. But I can’t just give it out for free because of the amount of time we have spent finding all the api calls, and breaking down the relevant responses.

I am presenting about it next week at the Peak of Data and AI actually, and using a webconnection example.

Feel free to private message me though, and we might be able to see what we can do in this instance.

​

david_r
bobw
2 people upvoted this
  • david_r
    david_r
  • bobw
    bobw
david_r
Evangelist
  • david_rEvangelist
  • April 28, 2025

In addition to the other excellent answsers here, I’d also like to mention the FMW reader that can analyze workspaces and extract the contents, such as referenced connections, including those that aren’t exposed as public parameters.

If you combine it with the Flow REST API, as demonstrated by Takashi above, it’s fairly easy to iterate over Flow repositories and download all workspaces before analyzing them.

takashi
bobw
2 people upvoted this
  • takashi
    takashi
  • bobw
    bobw
ebygomm
Influencer
Forum|alt.badge.img+32
  • ebygommInfluencer
  • Influencer
  • April 28, 2025
david_r wrote:

such as referenced connections, including those that aren’t exposed as public parameters.

 

Yes, if deployments have been a bit free and easy chances are there are connections that aren’t parameterised, public or private.

david_r
takashi
bobw
3 people upvoted this
  • david_r
    david_r
  • takashi
    takashi
  • bobw
    bobw
bobw
Contributor
Forum|alt.badge.img+5
  • bobwContributor
  • Author
  • Contributor
  • April 28, 2025

Great and prompt responses!  Thank you.
​@takashi, your well-formed and ready to run workspace is greatly appreciated and working well for me.

​@david_r, I forgot about the FMW reader but am now using it in conjunction with takashi’s workspace.

​@todd_davis, I’ll see you at the Peak, and specifically in the FME Flow: Secure and Clean presentation.

todd_davis
1 person upvoted this
  • todd_davis
    todd_davis

Reply


Helpful Members This Week

Community Stats

31,134
Posts
118,038
Replies
38,877
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.