Read Google Chat spaces for context, then post updates as approved steps
Connect Google Chat and Luumen can read the spaces your team already runs incidents in. It looks up space details, membership, message history, and read state to answer questions without you switching windows. Posting a message, adding someone to a space, or creating a space is a change, so it comes to you as a preview first. Authentication is OAuth2.
46 tools: 22 read, 24 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Google Chat run looks like inside Luumen.
Authorize once with OAuth 2.0. 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 complete space import, create custom emoji, create space member, create message, and more. 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 Google Chat — 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.