Skip to main content
Question

Getting a list of items, workspaces, automations etc from fme flow

  • March 21, 2025
  • 9 replies
  • 220 views

jackyd
Supporter
Forum|alt.badge.img+16

Hi everyone,

We are planning an fme upgrade shortly and I want to compile a list of the workspaces, automations and other items we have on our FME Flow instance to help plan for testing, and determining the amount of effort etc we will need to plan for.

Is there a way of doing this?

Does anyone have a process they can share?

Have had a look at using the api interface and http callers and could set something up with this, but hoping someone might have already done this that I could adapt for my systems. Or that there is a simpler native way that i have missed.

TIA

Jacky

9 replies

redgeographics
Celebrity
Forum|alt.badge.img+60
  • Celebrity
  • 3704 replies
  • March 21, 2025

I've been thinking of creating like a “FME Flow Quickscan” process, to do stuff like that: listing workspaces, connections etc. I haven't gotten around to doing it, but maybe I can whip something up in the next couple of weeks.


donalmateer
Safer
Forum|alt.badge.img+7
  • Safer
  • 43 replies
  • March 25, 2025

Hi ​@jackyd,

I don't think there's anything off hand - but some ways that you could go about it would be:

From the FME Flow Web UI:

  • Go to Repositories to view workspaces.
  • Go to Automations to view and export automations (.fmear).

If you want a full inventory, use FME Flow REST API:


FME Form with the HTTPCaller
Python script with requests

  • List repositories: GET /fmerest/v3/repositories
  • List workspaces: GET /fmerest/v3/repositories/{repo}/items
  • List automations: GET /fmerest/v3/automations (edited) 

Thank you!


alexbiz
Influencer
Forum|alt.badge.img+28
  • Influencer
  • 161 replies
  • March 25, 2025

You can export a backup, change the extension from fsbackup to zip and extract it. 
This will give you all the items as well as metadata to process that way.


redgeographics
Celebrity
Forum|alt.badge.img+60
  • Celebrity
  • 3704 replies
  • March 26, 2025

Toying around with it for a little bit, got a list of workspaces and users, is there anything else you'd want to see ​@jackyd ?


jackyd
Supporter
Forum|alt.badge.img+16
  • Author
  • Supporter
  • 62 replies
  • May 28, 2025

Thanks Everyone,
Will take a dive into the some of this
Need to a similar things with our Arcgis for Portal


jackyd
Supporter
Forum|alt.badge.img+16
  • Author
  • Supporter
  • 62 replies
  • May 28, 2025

Toying around with it for a little bit, got a list of workspaces and users, is there anything else you'd want to see ​@jackyd ?

 

Thanks Hans (@redgeographics)
Still working out what I need, but thinking I want automations and connections as well.
Trying to end up with a catalog of what we have and a reproducible process to help us keep track, particularly as we move towards a more self service model with our organisation. Trying to be in front of the curve and keep things to minor instead of major chaos


jackyd
Supporter
Forum|alt.badge.img+16
  • Author
  • Supporter
  • 62 replies
  • May 29, 2025

Hi Everyone,

I have a draft workbench that extracts lots of info from FLOW

Going add some reporting outputs to make it human readable and fit some process docs we have.
But it is on its way.

 


mgg_beca
Supporter
Forum|alt.badge.img+16
  • Supporter
  • 81 replies
  • October 15, 2025

Hi Everyone,

I have a draft workbench that extracts lots of info from FLOW

Going add some reporting outputs to make it human readable and fit some process docs we have.
But it is on its way.

 

This is useful thanks. ​@fme it would be great to have a documenter workspace included in the list of samples that spits out all info about flow that can be gleaned via the api - all schedules, automations, workspaces, dependencies etc.


jackyd
Supporter
Forum|alt.badge.img+16
  • Author
  • Supporter
  • 62 replies
  • October 16, 2025

Hi Everyone,

I have a draft workbench that extracts lots of info from FLOW

Going add some reporting outputs to make it human readable and fit some process docs we have.
But it is on its way.

 

This is useful thanks. ​@fme it would be great to have a documenter workspace included in the list of samples that spits out all info about flow that can be gleaned via the api - all schedules, automations, workspaces, dependencies etc.

Thanks ​@mgg_beca 

Yes, started looking at that, but was there quite a bit involved and I got deep into the weeds of doing the upgrade, hopefully I can get back to it at some stage, but happy for you to have a go and take this one further if you are interested.