Route specific external apis based on user-specific tasks. #672

Closed
opened 2026-02-21 17:27:58 -05:00 by yindo · 2 comments
Owner

Originally created by @yuhaowin on GitHub (Nov 8, 2023).

Originally assigned to: @takatost on GitHub.

Description of the new feature / enhancement

I experimented with the 'external_data_tool' feature and found that it's quite useful. However, I noticed that 'dify' consistently triggers external API calls whenever a user sends a message.

Scenario when this would be used?

As above.

Supporting information

No response

Originally created by @yuhaowin on GitHub (Nov 8, 2023). Originally assigned to: @takatost on GitHub. ### Description of the new feature / enhancement I experimented with the 'external_data_tool' feature and found that it's quite useful. However, I noticed that 'dify' consistently triggers external API calls whenever a user sends a message. ### Scenario when this would be used? As above. ### Supporting information _No response_
yindo added the 💪 enhancement label 2026-02-21 17:27:58 -05:00
yindo closed this issue 2026-02-21 17:27:58 -05:00
Author
Owner

@takatost commented on GitHub (Nov 17, 2023):

Yeah, that's how it's currently designed. We'll add an Agent auto-selection strategy later.

@takatost commented on GitHub (Nov 17, 2023): Yeah, that's how it's currently designed. We'll add an Agent auto-selection strategy later.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 2, 2023):

Close due to it's no longer active, if you have any questions, you can reopen it.

@github-actions[bot] commented on GitHub (Dec 2, 2023): Close due to it's no longer active, if you have any questions, you can reopen it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#672