Retool RPC

Connect to Retool's RPC service to seamlessly integrate your backend functions with Retool apps. Expose specific backend functions, manage permissions, and maintain version control while ensuring secure outbound-only architecture. Perfect for teams that need to extend their existing codebase into Retool apps.

Get Started with Retool RPC Docs

FAQs

Get answers to common Retool RPC questions

Retool RPC allows Retool apps to call functions defined in your own backend code, enabling teams to expose internal services, business logic, or private APIs to Retool without building a separate REST layer.

Retool RPC uses a server-side SDK that runs within your infrastructure and establishes outbound connections to Retool to poll for pending function calls. Your internal services are never directly exposed to inbound internet traffic.

Yes. Retool RPC is specifically designed for calling internal backend functions that should not be publicly exposed. The RPC server runs inside your network and uses outbound-only connections to Retool, so sensitive services remain behind your network perimeter.

Access to RPC resources is governed by Retool's role-based permission model. Admins can restrict which users or apps can invoke specific RPC functions.

Yes. Teams can deploy separate RPC agents for development, staging, and production, and configure Retool to use the appropriate agent per environment.

Retool RPC can call any function defined in the RPC agent—including database queries, internal APIs, microservices, scripts, or business logic—as long as the agent has access to those resources.

Build with your favorite tools

More integrations

Explore more Streaming integrations

Kafka (Beta)

Build real-time data streaming apps and monitoring tools