# Export workflow as JSON file **URL:** \ **Category:** HubSpot Ideas\ **Tags:** workflows\ **Created:** [June 8, 2021, 1:45pm UTC](https://community.hubspot.com/t/export-workflow-as-json-file/38545 "2021-06-08T13:45:13Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![CBludau](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cbludau/32/78108_2.png) [@CBludau](https://community.hubspot.com/u/CBludau)\ **Post date:** [June 8, 2021, 1:45pm UTC](https://community.hubspot.com/t/export-workflow-as-json-file/38545/1 "2021-06-08T13:45:13Z")
It would be very helpful to be able to export a workflow as a JSON file. The export to image is useful when sharing, but it lacks detail. In general, it would allow us to see all the detail of a workflow. For me, this would aid in the development of custom code modules where workflows are created. When creating a workflow in Operations Hub custom code, JSON is used to represent the workflow. ---
**Author:** ![CBludau](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cbludau/32/78108_2.png) [@CBludau](https://community.hubspot.com/u/CBludau)\ **Post date:** [January 18, 2022, 2:40pm UTC](https://community.hubspot.com/t/export-workflow-as-json-file/38545/2 "2022-01-18T14:40:05Z")
Update: It may have been obvious to everyone else, but I did find a workaround by using the HubAPI: [https://api.hubapi.com/automation/v3/workflows](https://api.hubapi.com/automation/v3/workflows). Adding the hapikey to the query string you can get a list of all workflows and workflow Ids. Adding a workflow gives the contents of the workflow, which can be copied and pasted to file, and easily read in a JSON editor. Stillm would be nice to do this from the site instead. [https://api.hubapi.com/automation/v3/workflows/?hapikey=yourkey](https://api.hubapi.com/automation/v3/workflows/?hapikey=yourkey) [https://api.hubapi.com/automation/v3/workflows/yourworkflowid?hapikey=yourkey](https://api.hubapi.com/automation/v3/workflows/yourworkflowid?hapikey=yourkey) ---
**Author:** ![ATroutt](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/atroutt/32/200694_2.png) [@ATroutt](https://community.hubspot.com/u/ATroutt)\ **Post date:** [August 13, 2025, 6:53pm UTC](https://community.hubspot.com/t/export-workflow-as-json-file/38545/3 "2025-08-13T18:53:22Z")
It would be great to be able to both export AND import the workflow config as json. This would enable better backups, validation, and source control for complex, mission critical workflows. ---
**Author:** ![VelocityOption](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/velocityoption/32/204176_2.png) [@VelocityOption](https://community.hubspot.com/u/VelocityOption)\ **Post date:** [March 23, 2026, 6:45am UTC](https://community.hubspot.com/t/export-workflow-as-json-file/38545/4 "2026-03-23T06:45:04Z")
Just giving this a bump and +1 in 2026. A lot of people _(including myself)_ do client work for different companies, and currently I have to manually configure thousands of actions for each client. This takes days. Import/Export should be considered a baseline requirement for any automation platform at this point. ---
**Author:** ![chrispomp](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@chrispomp](https://community.hubspot.com/u/chrispomp)\ **Post date:** [September 11, 2026, 10:34am UTC](https://community.hubspot.com/t/export-workflow-as-json-file/38545/6 "2026-09-11T10:34:12Z")
100% agreed ---
**Author:** ![KennyWu](https://avatars.discourse-cdn.com/v4/letter/k/a4c791/32.png) [@KennyWu](https://community.hubspot.com/u/KennyWu)\ **Post date:** [September 29, 2026, 6:19pm UTC](https://community.hubspot.com/t/export-workflow-as-json-file/38545/7 "2026-09-29T18:19:46Z")
_Hi everyone!_ _I’m Kenny, a Product Manager for HubSpot’s Automation platform._ _Thank you for taking the time to share this idea — we genuinely read and consider everything submitted here._ \*After review, we don’t have plans to build this right now. A JSON export is not as simple as it might seem, because workflows reference portal-specific IDs for properties, lists, users, etc. that don’t travel well outside of a portal. That said, we revisit our roadmap regularly, and customer ideas like this one do influence what we prioritize. If you’re interested in staying in the loop on what we are building, feel free to grab some time with me: [[meeting link]](https://hubspot.com/meetings/kenny140).\* _Thanks, Kenny_