workflow as a code #22219

Open
opened 2026-02-21 20:16:12 -05:00 by yindo · 0 comments
Owner

Originally created by @matteo-rama on GitHub (Feb 13, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Hello,

it will be intresting to be able to save/load a workflow using some sort of API.
this will enable a sort of "versioning" of workflow and a release cycle using a pipeline.

example
in dify "test" i will draw my workflow, test it, modify it. I store it in a json (yaml, anything) and store in git.
this workflow is the ready to be loaded in another dify instance of production via CI/CD pipeline, where access is given only to selected and limited user.

This kind of segregation is intresting to avoid modifying workflow in production without having an "approval" step from someone.

Also it allow a sort of versioning, because a pipeline can rollback to a specific git tag, everything is 'stored' and we can operate with a devops like approach.

It's also intresting to have the export function (export a workflow to a json) in a pipeline, to have a fully automated process.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @matteo-rama on GitHub (Feb 13, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Hello, it will be intresting to be able to save/load a workflow using some sort of API. this will enable a sort of "versioning" of workflow and a release cycle using a pipeline. example in dify "test" i will draw my workflow, test it, modify it. I store it in a json (yaml, anything) and store in git. this workflow is the ready to be loaded in another dify instance of production via CI/CD pipeline, where access is given only to selected and limited user. This kind of segregation is intresting to avoid modifying workflow in production without having an "approval" step from someone. Also it allow a sort of versioning, because a pipeline can rollback to a specific git tag, everything is 'stored' and we can operate with a devops like approach. It's also intresting to have the export function (export a workflow to a json) in a pipeline, to have a fully automated process. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 20:16:12 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#22219