Check OneSignal users, devices, and segments, then change subscriptions with approval
Connect OneSignal and your agent can answer questions about who is reachable and who is not. Look up a user by alias, read a device record, check segment sizes, review broadcasts and outcomes. When something needs fixing — a stale subscription, a wrong device attribute — the change is previewed and held for your approval before it runs.
12 tools: 8 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed OneSignal User Auth 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.
This connection exposes write actions such as create or update onesignal user, delete user alias, edit onesignal device, update subscription by token. 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 OneSignal User Auth — 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.