1) Please have an option to include further details when exporting workflows as images. For example, the details of which specific contact owners are rotated amongst would be helpful to export.
2) Alternatively, or in addition, please add an option to export the entire workflow (including all details) as CSV files (instead of images).
Both of the above can assist with repairing or reverting a workflow after any unwanted edits, and are likely easier and quicker to use than attempting to see what happened via the cumbersome revision history.
While we would love to add more details to the export image, we are often constrained by the size of large workflows and therefore need to adjust the size of our graph to accommodate workflows with many actions. That being said, I'd like to dig a bit more into your use case for exporting the workflow to a saved format, such as a CSV file.
What kinds of information would you expect to be contained in the file? Would you want to manually read it, or would it be enough to be able to "upload" the workflow into HubSpot without needing to actually understand the contents of the file? Are there any other use cases you can think of that might be helpful?
While we would love to add more details to the export image, we are often constrained by the size of large workflows and therefore need to adjust the size of our graph to accommodate workflows with many actions. That being said, I'd like to dig a bit more into your use case for exporting the workflow to a saved format, such as a CSV file.
What kinds of information would you expect to be contained in the file? Would you want to manually read it, or would it be enough to be able to "upload" the workflow into HubSpot without needing to actually understand the contents of the file? Are there any other use cases you can think of that might be helpful?
I want to test new or modified workflows in the sandbox before deploying them to production. An export/import feature for single workflows would be very helpful there. The produced file would not have to be readable or editable, but it should contain all possible workkflow actions, including custom code actions (and also beta actions). As an alternative, a "synch" feature from sandox to production for selected items (like single workflows) would be handy. Since such a feature already exists in the oposite direction (production to sandbox), it does not seem impossible to achive.
Thanks for considering,
Ekki
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
.png "HubSpot Employee"){kind=icon}
