This flowpack polls the Okta System Log at regular intervals and looks for the workflows.user.flow.save event and backs up any updated flows to Google Drive (easy to swap this out with GitHub, Box, OneDrive, etc).
I know some Workflows customers have built similar flows to this, but based on some conversations I had at Oktane this year I figured I’d provide my take on the use case. I was hoping to do this in two flows, but it takes three to make sure you’re not backing up the exact same flow more than once.
This has only been tested by the flow author, so feel free to report any issues in the replies and/or post your own version of the flowpack. Happy flowgramming!
Downloaded, implemented, and (some) flows are now backed up… any flow that doesn’t make it into an original list of 200 events in the last 90 days (I set the original value in the table to now-90) wouldn’t be backed up… correct?
As far as organizing these into folders, I’ve seen some hacky ways to get the folder data downloaded with Rockstar, uploaded to a table, and then using that table as the source of truth for the backups… not super clean but with the flow you shared it’d be pretty comprehensive.
Any chance we can get a Read Workflow Metadata card? This would be really cool for a number of reasons. I can see the file ‘Description’ in Google Drive being populated by the flow’s Description field for example, and of course for folder organization. Maybe not immediately, but when it comes to which flow calls which helper flow… I can see this helping unearth dependencies.
I’m sure there’s an idea for this out there already… I’m going to see about finding it and upvoting it.
