Support agent node in a workflow

[yc3231996]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• 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.

in current workflow design, we can add LLM or tools as nodes, but can't configure LLM node to call tools just like agents do.

2. Additional context or comments

No response

3. Can you help us with this feature?

• I am interested in contributing to this feature.

[hllshiro]

I need this too. The main purpose is to divide the process in two parts: Q&A guidance and result generation. Their prompts are the same, but the latter only outputs json_object

[hllshiro]

It seems that it can be implemented using node HTTP Request. The API interface will be provided after the agent is released.

[yc3231996]

it is more like a multi-agent requirement. I.E, in a workflow, an LLM node with ability of function calling is basically an agent.
It is the same thing to support choosing an agent as a node in a workflow.
It would be helpful to have multi agents work together, even simply in a sequential mode.
I am not running into complex situation that has to have a commander or manager agent to coordinate worker agents (like the hierarchical mode in CrewAI), but chain agents one after another is what I am trying to achieve.

[yc3231996]

It seems that it can be implemented using node HTTP Request. The API interface will be provided after the agent is released.

do you mean call another agent via HTTP request in workflow? it is smart, would be good if have this as a built-in feature.

[hllshiro]

do you mean call another agent via HTTP request in workflow? it is smart, would be good if have this as a built-in feature.

Yes, since dify doesn't provide an agent node at the moment, can only use this method to finish my job. Of course, I also agree that would be good if have this as a built-in feature

[kenneth-bro]

+1

[alterxyz]

Sounds like "Agent as Tool", sounds good.

[softgoto]

+1

[wltj920]

+1, We need "ReAct agent tool" that other agents can calling it to do something. Any agent can called by any agents.

[sapipoZZZ]

+1

[GuoNingNing]

+1

[EcoleKeine]

@crazywoola Are there any plans to add this feature?
Can't use Agent in workflow by http request, agent http Api not support blocking mode

[aijak69]

.

[aijak69]

@crazywoola Are there any plans to add this feature? Can't use Agent in workflow by http request, agent http Api not support blocking mode

You can use code block to parse the output for now

[infinitnet]

+1, just wanted to open a feature request for this as it seems logical that it should be possible to use agents in workflows. This way agents would be like an LLM + tool combination repository and workflows could be used to put these parts together, which is especially useful if someone re-uses the same sets of LLM + tool combinations (ie. "agents") within various workflows.

[neotize]

+1，Additionally, I hope that the Agent nodes can support the 'Add Message' feature (customizable multi-turn USER and ASSISTANT dialogues), to achieve a few-shot effect.

[MengXiangyu0624]

+1

[chou852ishare]

+1

[bejay2vwo]

+1

[dadastory]

I really need it, it's so important for a knowledge chat workflow app

[OraCatQAQ]

+1

[cloover]

+1

[LNZ001]

这是来自QQ邮箱的自动回复邮件。已收到~

[hoomjac]

+1

[lins403]

+1

[shuxinhuang]

+1

[kinglisky]

+1

[jinxianwei]

+1

[eightHundreds]

+1

[LNZ001]

这是来自QQ邮箱的自动回复邮件。已收到~