Rudder Lookout is currently in Public Beta. Contact the Product team if you have any questions.
Lookout is most useful when it is connected to the systems your team already uses. Each integration plugs a real tool into the agent. Connect a warehouse and the agent can query it; connect a repository and it can read it.
The agent only touches a system that is configured for your workspace.
You connect most tools from Settings, where the integrations are spread across a few tabs. External AI tools are set up from Settings > Integrations.
| Tool | What it unlocks |
Where to connect | Who can connect? |
|---|---|---|---|
| RudderStack | Activate audiences to your destinations, and read sources, transformations, and Tracking Plans. | Linked when the workspace is created | Workspace creator |
| Warehouses | Ask questions of your data and build audiences from it (read-only). Link repositories to a warehouse here. | Settings > Connections > Warehouses | Admin |
| GitHub | Read repositories for context — files, commits, and pull-request diffs. | Settings > Connections > Source Control | Admin — any member uses repo tools |
| Slack | Chat with the agent from a Slack DM or a bound channel. | Settings > Integrations | Admin |
| External AI Tools | Let approved external AI tools call a curated set of Lookout’s tools. | Settings > Integrations | Any member — if enabled for your deployment |
See Integrations for full capability and setup details.
Your RudderStack workspace is linked when you create the Lookout workspace, so the first thing to add is a warehouse — it is what lets the agent answer questions about your data and build audiences from it.
From there, add integrations as your team needs them:
Most connections are made by a workspace admin. Connecting a system is a workspace-level decision — once connected, the agent can use it on behalf of any member.
See Roles and Permissions for more details.