Skip to content

feat: support custom connection data arg in execute proxy and tool#1766

Merged
haxzie merged 7 commits intonextfrom
feat/support-custom-connection-data
Jul 21, 2025
Merged

feat: support custom connection data arg in execute proxy and tool#1766
haxzie merged 7 commits intonextfrom
feat/support-custom-connection-data

Conversation

@lingalarahul7
Copy link
Copy Markdown
Contributor

@lingalarahul7 lingalarahul7 commented Jul 18, 2025

Previously, we were taking custom auth parameters as full headers and query params.
But now, we stopped sending the proxy field 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 customAuthParams arg and will support both for the foreseeable future, but would highly recommend using customConnectionData.

We are implementing this for both cases - custom tools and composio managed tools!

@lingalarahul7 lingalarahul7 force-pushed the feat/support-custom-connection-data branch from 741678a to ae9841d Compare July 21, 2025 09:12
@haxzie haxzie merged commit cea1b48 into next Jul 21, 2025
7 checks passed
@haxzie haxzie deleted the feat/support-custom-connection-data branch July 21, 2025 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants