Skip to main content
Warehouse connectors let Replit Agent securely query your organization’s data warehouses. Builders use natural language to create dashboards, reporting tools, and data applications — no SQL expertise required. Admins keep centralized control with role-based access.

​
Supported warehouses

Warehouse connectors are available on Enterprise plans. Each warehouse has its own setup flow because the OAuth integration, identity model, and credential format differ. Pick the warehouse you use and follow its dedicated guide.

​
Analytics and data platforms

Analytics connectors are available on Core and Pro plans alongside Enterprise. Connect your analytics tools so Agent can read and work with your product data:
  • Segment — Customer data, event streams, and audience segments from your CDP
  • Amplitude — Product analytics, user behavior data, and engagement metrics
  • Hex — Collaborative data notebooks and query results
Manage these the same way as other Replit connectors. See Managing your connectors.

​
How warehouse connectors work

Setup is a one-time process that involves three roles:
  1. Warehouse admin — Creates an OAuth integration or service identity in the warehouse
  2. Replit organization admin — Adds the credentials to Replit and configures access
  3. Builder — Signs in and starts building with Agent
Once configured, builders ask Agent to use the warehouse and Agent writes and executes SQL against it.

​
Building with warehouse data

After connecting, you can ask Agent to build applications that use your data. Agent can:
  • Build internal tools that fetch and display live data
  • Create dashboards with charts and visualizations backed by your warehouse
  • Generate SQL queries to power your application’s backend
  • Explain schema and table structures to help you understand what to build
While Agent can answer ad-hoc questions about your data, the primary purpose of warehouse connectors is to enable Agent to build functional applications that leverage your organization’s data. Warehouse queries are executed directly against your instance, so make sure your OAuth scopes and database user permissions allow the necessary read and write operations.

​
Connector availability