Backup - Anyway To export my App Structure and Automations

So I wrote alot of code for my automations and I was thinking, I should really back everything up to my hard drive or a S3 bucket. Is there anyway I can export Automations and my App structure?

P.S I would like to avoid using any third partys due to security concerns.

Thanks :grinning:

1 Like

Hey :slightly_smiling_face: just wondering if anyone has a solution?

Yes - ProBackup!

They have been around forever. I’ve used them quite a bit for my Podio clients and they’re great.

1 Like

Hi :grinning: so I spoke everything out with my partner. He does not want me to use a third party for backups. Is there anyway I can export my code similar to how it is done in Podio?

I would be willing to do my backups using the Tape API. I can’t use a third for security concerns. What would be the best way to go about doing this with the API? The data will be backed up to our server.

Thanks

Depends what you class as a third party? You could easily sync your data real time to a Supabase DB and have it all stored there.
Everything seems overkill really. Tape is technically a ā€˜third party’ and your data is stored there. I don’t see the difference between having data in Tape and having data in a different secure third party like ProBackup.

4 Likes

I agree. I would think that trying to secure data internally would be a difficult task when it comes to security patches and vulnerabilities.

1 Like

Thanks! So regarding Tape I trust Tape. I know the team is onto something VERY BIG here. The whole thing that gets me is having to give an additional third party Permanent API access to backup my data. I know it’s convenient, but it’s not very secure. I would much rather write my own code and store the data to my own server. It will help me sleep better at night :smiley: @1F2Ns Regarding security patches and vulnerabilities, I will be storing everything to a AWS S3 bucket.

Now regarding my automations and calculations I’ve spent over a month writing the code. It would be really cool if there was an export button in the automation section, so I can dump all my automations and save them to my hard drive. I definitely think having a button to export automations should be a feature. Although Tape blows Podio away Podio does have this feature. I personally think this feature is a must.

1 Like

I got you. I thought you were looking to store everything on location.

Make sure you add that as a future request.

1 Like

I am all for a nice simple way to backup automations or a Workflow API.
However until that comes along don’t forget you can duplicate a workspace which will copy the whole app structure and automations associated with the apps this can even be done cross organisation:

video here

8 Likes

Thanks Jason! that’s awesome :grinning: that seems solid for now :+1:

1 Like

Obviously if you use the publish to a new organisation as i show in the video rather than a simple duplicate remember to un-publish when you done :wink:

1 Like

Awesome! Thanks Jason :grinning:

Hi All, I’m using ProBackup for Tape but I have just realised it doesn’t restore files nor workflows, which a major handicap. Does anyone know of any other service that provides this level of protection?

Tape’s Automation tool doesn’t have an API so it’s not possible to backup workflows at current. However, I have been writing more and more workflows using raw JS in an Execute Script function so it makes it super easy to copy and paste workflows in between apps.

2 Likes

Late to this thread, but there’s an update worth adding — and a gap that I think is bigger than the one being discussed.

On automations: the situation has changed. There is an Automation API in beta now. We’ve been using it to export automations as versioned JSON, one file per app, committed to Git. So the ā€œno API for workflowsā€ limitation is being lifted (it might be beta release yet).

For app structure, GET /v1/app/{appId} already gives you everything: fields, types, configs, slugs. We drive our whole deployment engine off that shape — read an environment, produce a JSON definition, replay it into another org. Which means backup and provisioning end up being the same problem solved once.

But here’s what none of us can back up: permissions.

@RichardHedger’s point about ProBackup not restoring files or workflows is the right kind of worry, and I’d extend it. There is no API to read permissions at any level — not for workspaces beyond membership, not for apps, not for records. I checked this fairly thoroughly: every candidate REST path returns 404, and the automation SDK exposes batchUpdatePermissions for writing record permissions but nothing at all for reading them.

So even a perfect backup of structure, data and automations restores into an environment where nobody has the right access, and there is no way to reconstruct what it was. For anyone with guests or granular sharing, that’s a silent hole in the DR story.

Would love to see read access for permissions on the roadmap — it’s the one piece that makes the rest of a backup actually restorable.

:brazil: Toni