How to Connect RudderStack Control Plane to Lookout Private Beta

Connect your RudderStack control plane to Lookout so you can read and manage it from chat.

Connecting RudderStack to Lookout lets the agent read and manage your control plane from chat — including your sources and destinations, transformations, Tracking Plans, and Audiences.

Connect RudderStack

Signing in to Lookout with RudderStack is recommended.

When a user creating the workspace signs in with RudderStack, Lookout automatically pulls in the list of RudderStack workspaces they belong to — so linking a Lookout workspace to the right RudderStack workspace takes a single click.

When you create a workspace with this method, Lookout shows the RudderStack workspaces you are part of:

  • Link: Create a Lookout workspace connected to that RudderStack workspace
  • Join: If your team already uses a Lookout workspace for that RudderStack workspace, join it so everyone’s chats and dashboards stay together (or choose to create a separate workspace instead)
Picking a RudderStack workspace to link when creating a Lookout workspace

Connect manually

Though signing in with RudderStack is the recommended approach, a workspace admin can also connect manually under Settings > General by entering a RudderStack Workspace ID and Personal Access Token. The connection is scoped to your workspace and the token is stored encrypted.

info

The RudderStack connection is configured once per workspace. Once connected, any member can use the RudderStack tools in chat. Connecting it is therefore a workspace-level decision.

See Roles and Permissions for more details.

How it works

Once a RudderStack connection is set up, the agent can:

  • Inspect sources, destinations, transformations, Tracking Plans, and Audiences
  • Review live event metrics, schemas, and Tracking Plan violations
  • Make changes — for example, create or update a transformation or an Audience
info

Important consideration

Whether the agent can make changes depends on how the connection is authorized. A read-write RudderStack connection enables the management tools above. However, a read-only connection — for example, a workspace linked with a read-only token — limits the agent only to inspecting and reporting.

Once a RudderStack connection is set up, the agent can answer questions and make changes that span your warehouse data and your RudderStack configuration in the same conversation. For example, checking how an event is defined in a Tracking Plan and where it lands in the warehouse.


Questions? We're here to help.

Join the RudderStack Slack community or email us for support