Export and Import Workflows Within The Workflow Automator

100%! Especially, when you have to create similar workflows in different Workspaces, that should work on a Workspace level, not on a Global level.
Another case for us as an integrator is to create similar workflows for different customers, which takes a lot of time. If we could maintain our own library of workflows that we often use and then just import them to new projects, it would be great.

Just going to selfishly bump this one and suggest something that may be easier to implement in the short term:

From an individual Workspace, when clicking the ‘Clone’ button, a drop-down could appear either directly beneath the Clone button or in the resulting dialogue…

...whereby you can select ‘Clone To...’ - the purpose being; you can select a different Workspace to clone this individual Workflow to.

I understand that the resulting Clone in a different Workspace will almost certainly require tweaking/fixing prior to activating but it will at least have the majority of the, already built, required logic and will remove a lot of the frustrations involved in handling multiple Workspaces.

Exporting a list of all workflow automations would also help public companies with their audits. Automations surrounding in-scope activities or systems fall under audit review. Rather than manage an external spreadsheet with a list of automations, it would be nice to export it directly from FS so we can determine which are/aren’t in-scope.

This feature would be very useful for people who accidentally created Global Workflows and meant to do them in a Workspace.   Theoretically I mean…..

I’ve been hunting a solution for this also - if you expect to have complex workflow automations in here you should have a way to document and audit them efficiently. 

We are currently using the PRO plan and therefore do not have a dedicated sandbox environment. For this reason, we operate a second instance that serves as a test environment.

A workflow export and import feature would be of great assistance to us, as it would allow changes and new developments to be transferred much more efficiently between the test and production environments.

Furthermore, we believe it would be very helpful if generally useful workflows were made available as templates—either via the community or directly by Freshworks. This would reduce implementation effort and make it easier for many customers to get started with automation.