Rudder Lookout is currently in Public Beta. Contact the Product team if you have any questions.
Each Lookout integration plugs a real tool into the chat agent, so you can ask for something in plain language and the agent acts through the same connection you would use yourself.
The agent can only touch a system when that integration is configured for your workspace, and the surface it gets is exactly what the integration provides. With nothing connected, the agent can still chat — it just has no external reach.
The Lookout integrations fall into two groups:
| Integration | What it unlocks |
|---|---|
| Warehouses | Ask questions of your warehouse in natural language. Lookout supports PostgreSQL, Snowflake, Redshift, BigQuery, Databricks, and ClickHouse currently, with read-only access |
| GitHub | Read repositories for context — files, commits, and pull-request diffs |
| RudderStack | Read and manage sources, destinations, transformations, Tracking Plans, and Audiences configured in RudderStack |
| Link Repositories to Warehouses | Link GitHub repositories to a warehouse so the agent knows which code describes which data |
| Slack | Chat with the agent from a Slack DM or a bound channel |
| External AI Tools | Let approved external AI tools call a curated set of Lookout tools through the Lookout MCP |
Each integration is wired into the agent only when it is configured. Warehouse tools appear once a warehouse is connected, and repository tools appear once repositories are linked. You connect a system once, and the same connection powers chat, dashboards, audiences, and Slack.
Most integrations are connected by a workspace admin, because connecting a system is a workspace-level decision. Once connected, the agent can use it on behalf of any member.
See Roles and Permissions and Security and Data Handling for more details.