feat: support custom connection data arg in execute proxy and tool#1766
Merged
feat: support custom connection data arg in execute proxy and tool#1766
Conversation
741678a to
ae9841d
Compare
angrybayblade
approved these changes
Jul 21, 2025
haxzie
approved these changes
Jul 21, 2025
haxzie
approved these changes
Jul 21, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, we were taking custom auth parameters as full headers and query params.
But now, we stopped sending the
proxyfield in our toolkit details endpoint and hence customers don't know the shape of the headers nor the base url, hence making it difficult for them to know the format expected.So to make it further easier, we now only take the field values as input and we figure out the headers and base url shape internally and call the tools.
The new arg is
customConnectionData.We are not immediately deprecating
customAuthParamsarg and will support both for the foreseeable future, but would highly recommend usingcustomConnectionData.We are implementing this for both cases - custom tools and composio managed tools!