Read contacts, services, and broadcasts in Whautomate, then change them with approval
Connect Whautomate and Luumen can read your customer engagement setup from the terminal: contacts, segments, broadcasts, services and categories, staff availability, and registered webhooks. Changes such as adding a contact or updating a service are previewed first, then applied as an approved, audited step. Luumen authenticates with an API key.
17 tools: 13 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Whautomate run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add contact, delete segment, delete service category, update service — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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 Whautomate — 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.