I'm trying to build a hybrid agent in Dify using Chatflow to handle a wide variety of tasks. My plan is to design each task as a separate workflow. In Chatflow, I’d determine the user’s intent and then route it to the corresponding workflow node to execute the specific task. However, the current workflow design is meant for single tasks and doesn’t support variables, and the LLM lacks memory capabilities. As a result, I have to pass the conversation ID to the workflow and store the variables generated by the workflow, along with the conversation history, in a third-party service like Redis. While this works, it makes the workflow overly complicated. If workflows could support variables, things would be much simpler. Do you have any good suggestions for a better approach?
Log in to comment and vote
Comments3
chln
Mar 27, 2025
workflow variables support please!
evanchen
Apr 1, 2025
Tell me how you want to use it?
chln
Apr 1, 2025
I'm trying to build a hybrid agent in Dify using Chatflow to handle a wide variety of tasks. My plan is to design each task as a separate workflow. In Chatflow, I’d determine the user’s intent and then route it to the corresponding workflow node to execute the specific task. However, the current workflow design is meant for single tasks and doesn’t support variables, and the LLM lacks memory capabilities. As a result, I have to pass the conversation ID to the workflow and store the variables generated by the workflow, along with the conversation history, in a third-party service like Redis. While this works, it makes the workflow overly complicated. If workflows could support variables, things would be much simpler. Do you have any good suggestions for a better approach?