langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 09:10:05 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Support Dynamically Setting Tool API Keys via Session Variables #14683

New Issue
Closed
opened 2026-02-21 19:18:18 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 19:18:18 -05:00
Owner
Copy Link
Copy Source

Originally created by @wukaikailive on GitHub (Jun 17, 2025).

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.

It is desired to support the dynamic setting of API keys for tools. For instance, a user's dynamically generated authentication key (produced within a workflow) or one passed from the user's request could be stored in a session variable. The goal is to then reference this session variable in a tool's API key configuration field using the {{<var_name>}} syntax.

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 @wukaikailive on GitHub (Jun 17, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [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. It is desired to support the dynamic setting of API keys for tools. For instance, a user's dynamically generated authentication key (produced within a workflow) or one passed from the user's request could be stored in a session variable. The goal is to then reference this session variable in a tool's API key configuration field using the {{<var_name>}} syntax. ### 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 💪 enhancementperformanceProposal labels 2026-02-21 19:18:18 -05:00
yindo closed this issue 2026-02-21 19:18:19 -05:00
yindo commented 2026-02-21 19:18:19 -05:00
Author
Owner
Copy Link
Copy Source

@wukaikailive commented on GitHub (Jul 3, 2025):

Do you have any development plans? @alterxyz

@wukaikailive commented on GitHub (Jul 3, 2025): Do you have any development plans? @alterxyz
yindo commented 2026-02-21 19:18:19 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 26, 2025):

Hi, @wukaikailive. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested a feature to support dynamic setting of tool API keys via session variables using {{<var_name>}} syntax.
  • This feature aims to allow API keys generated during workflows or passed in user requests to be referenced dynamically.
  • You asked about development plans and tagged @alterxyz for input.
  • There have been no updates or responses from the maintainers since your inquiry.
  • The issue remains unresolved and open for discussion.

Next Steps:

  • Please let me know if this feature request is still relevant to the latest version of Dify by commenting on this issue.
  • If I do not hear back within 15 days, the issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 26, 2025): Hi, @wukaikailive. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested a feature to support dynamic setting of tool API keys via session variables using {{<var_name>}} syntax. - This feature aims to allow API keys generated during workflows or passed in user requests to be referenced dynamically. - You asked about development plans and tagged @alterxyz for input. - There have been no updates or responses from the maintainers since your inquiry. - The issue remains unresolved and open for discussion. **Next Steps:** - Please let me know if this feature request is still relevant to the latest version of Dify by commenting on this issue. - If I do not hear back within 15 days, the issue will be automatically closed. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:18:19 -05:00
Author
Owner
Copy Link
Copy Source

@wukaikailive commented on GitHub (Aug 27, 2025):

This function is still needed.

@wukaikailive commented on GitHub (Aug 27, 2025): This function is still needed.
yindo commented 2026-02-21 19:18:19 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 27, 2025):

@crazywoola The user has confirmed that the feature request for dynamic setting of tool API keys via session variables is still needed. Could you please assist with this issue?

@dosubot[bot] commented on GitHub (Aug 27, 2025): @crazywoola The user has confirmed that the feature request for dynamic setting of tool API keys via session variables is still needed. Could you please assist with this issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label Proposal performance 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#14683
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?