OneSignal User Auth
for LuumenAI

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.

Book a DemoDownload Luumen

The OneSignal User Auth toolbox

12 tools: 8 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadView OneSignal SegmentRetrieve the subscriber count for a specific OneSignal segment.
  • ReadView AppRetrieve details for a specific OneSignal app.
  • ReadView BroadcastsView inbox broadcasts for a OneSignal app.
  • ReadView OneSignal DeviceRetrieve details for a specific device/player.
  • ReadView OutcomesView all outcomes associated with a OneSignal app.
  • ReadView SegmentsList all segments for an app.
  • ReadView OneSignal UserRetrieve user details by alias label and ID.
  • ReadView User Unread Message CountRetrieve the unread message count for a specific user.
  • WriteCreate or Update OneSignal UserCreate a new user or modify the subscriptions associated with an existing user. Approval by default
  • WriteDelete User AliasRemove an alias from a OneSignal user. Approval by default
  • WriteEdit OneSignal DeviceUpdate an existing OneSignal device (player) record. Approval by default
  • WriteUpdate Subscription By TokenUpdate properties on an existing subscription using its token. Approval by default

One prompt, start to finish

What a governed OneSignal User Auth run looks like inside Luumen.

Questions

How does LuumenAI connect to OneSignal User Auth?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in OneSignal User Auth on its own?

Read actions answer immediately. Anything that writes — create or update onesignal user, delete user alias, edit onesignal device, update subscription by token — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

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.

Is there an audit trail?

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.

All integrations
SlackRead the incident thread; post updates and approvals back.GmailVendor and alert mail as context; replies drafted for review.Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.DiscordRead Discord command permissions and app context, then change them with approval

Put OneSignal User Auth to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.

Book a DemoDownload Luumen