Agentflow v2 and API vars #4695
Unanswered
fpmirabile
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Flowise team!
I’m working on a use case that involves sending sensitive data via the API, specifically for tools like Calendar, Drive, etc., to function per user. In my scenario, I want to pass the bearer token manually into a semi-configured tool (only clientId and clientSecret set), then provide the access_token programmatically.
In my code, I’ve implemented something like this:
This works perfectly in Chatflow.
However, I noticed that in Agentflow, this same override doesn’t work when using tools within agent nodes. After some debugging, I found that the variables weren't being passed through correctly.
Looking into the agent node code, I realized that the construction of
newNodeData
was missing thevars
. So I added the following line:Adding that line fixed the issue.
It seems like
toolConfig
is sending an empty vars object, which is likely why it wasn’t working. My question is:Is this the expected behavior in Flowise for Agentflow, or is this an unintended omission?
Thanks for the amazing work — Flowise has been a huge help in building workflows! 🙌
Beta Was this translation helpful? Give feedback.
All reactions