Hello from the Retool team. We're exciting to introduce into beta a feature we're calling Retool RPC, which lets you connect your own codebase to Retool, allowing you to define functions in your backend and call them in Retool apps and workflows. It's something we think can be pretty powerful for a number of use cases, but we'd love to hear from folks in the community who might be trying to solve this problem today.
To see Retool RPC in action in a video and read a walkthrough, you can follow this quickstart guide on our docs: Retool RPC quickstart | Retool Docs
If you're interested in Retool RPC because it solves a problem you're having with integrating Retool into your existing codebase, we'd love to hear from you! We'll be rolling out Python support in addition to Node shortly, but we're excited to see how this can be compelling from the community.
When there is a python SDK available, I will be one of the first ones to sign up!!
Any news on the SDKs in other languages? In docs I can see you are planning to roll out support for many other languages and I am hoping python will make the cut
Hey there - we're trying to use the Retool RPC product in Typescript but are unable to deploy it to a production environment because of a package issue. There is an open issue on Github that has been created with exact reproduction steps to troubleshoot the issue we're seeing: SyntaxError: Named export 'RetoolRPC' not found. · Issue #11 · tryretool/retoolrpc · GitHub
Would really appreciate if this could be looked at so we can continue adoption, as Retool RPC seems like a great devex for our internal endpoints. Thanks.
@jqh100 Actually, looks like there is some issue with using "ESBuild" and --format=esm. We can take a look at that later. But for now, you can change the "target" of ESBuild to use --format=cjs and it would work.
See my change here for example & See more on the github issue for detail: