In n8n I can download a flow as a JSON file and re-upload it elsewhere when needed. If I remember it correctly Miro also has this feature. This is pretty useful especially when I’d like to preserve (or save for later) a certain data model without the need to keep the actual data in Fibery. Later, if necessary, I’d want to be able to import that back into Fibery.
You can always export your workspace as a template (with or without entities) which generates a URL. Using this URL you can recreate the workspace at any later time.
I wonder why you specifically want a JSON formatted file for this process?
On the other hand, if you merely want a file which represent the workspace structure (aka data model) you can query the schema using the API and store the output.
But this file cannot then be used to recreate a workspace from scratch.
I was meaning specifically that. I don’t care tbh about the exact format, as long as I could later re-import that into Fibery when needed so that I don’t overload my space with something I don’t use right now but may use again in a certain period of time, eg for another client.
If you don’t care about the format, what are the deficiencies with the current mechanism for creating workspace templates?
It’s not about sharing. It’s about managing. Currently, I have 2 agency models in my workspace and plan to create another one for a different kind of business. For general Fibery users this case may not be valid but for partners implementing workspaces for different niches it can and is for me.
This idea came out of the problem with the following.
When I look at User db, it just scares me to see the amount of different relations with similar names, like Company (related to agency1), Company (related to agency2), there will also be Company (related to a different kind of niche), Contact, Contact, etc. To easily distinguish between the different similar db names, I decided to add suffixes, like Company, Company Adv (from Advanced). Maybe this is suboptimal though - I haven’t decided on that yet.
A typical Fibery client won’t have this issue.
And so I thought: what if I could simply create the workspace, deploy it to the client’s environment (via sharing) and then archive so to speak or download on my pc so that later when necessary I could re-upload it back to Fibery.
I think it is not likely that we would make templates available as downloadable files (never say never!) but I don’t understand why you don’t just create workspaces for each use case.
In other words, you can be admin for multiple workspaces (one per agency model) and every time a client comes along you use the sharing mechanism to clone one of them (whichever is suitable for the client).
Adding note here for future readers that the solution above (save each template as a workspace) was discussed via email, and works well.
(the cost of managing these workspaces need not be problematic - Fibery partners can apply for free ‘sandbox’ workspaces)
1 Like