Read transformation code and versions, then publish changes as approved steps.
Connect RudderStack Transformation and Luumen can read the transformations and libraries in your workspace, pull the code behind any revision, and compare versions before anything changes. When you ask for an edit, it drafts the new version, shows you the code, and waits for your approval to publish. Basic auth.
12 tools: 8 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed RudderStack Transformation run looks like inside Luumen.
Authorize once with Basic auth. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create library, create transformation, delete transformation, update transformation. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to RudderStack Transformation — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.