OneSignal User Auth logo
ConnectorOneSignal User Auth

OneSignal User Auth integration for Claude and Codex

Create a OneSignal User Auth connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Use OneSignal User Auth from Claude

Add the OneSignal User Auth connection to a Space that runs Claude, then use it from every channel in that Space.

Use OneSignal User Auth from Codex

Add the OneSignal User Auth connection to a Space that runs Codex, then use it from every channel in that Space.

Use OneSignal User Auth from Sidekick

Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.

Email & Messaging

What the OneSignal User Auth connector can do

OneSignal User Auth handles identity verification and subscriber management behind OneSignal's push, email, and SMS messaging. Connected to a type.com Space, the agent can register or update a user, adjust a device record, or check how many subscribers sit in a segment, so engineering and lifecycle teams can troubleshoot messaging issues in one shared thread.

One connection, many Spaces

Connect OneSignal User Auth once, then decide which Spaces can use it in threads, skills, automations, and coding work.

What teams do with OneSignal User Auth in type.com

Fix a subscriber's messaging settings

Update a user's subscriptions directly when a customer reports they stopped receiving notifications.

Try asking
Update the OneSignal user for this customer to re-enable their push subscription.

Clean up a duplicate alias

Remove an outdated alias from a user record while keeping their other identifiers intact.

Try asking
Delete the old alias on this OneSignal user but keep their current external ID.

Check segment size before a send

Confirm how many subscribers a segment actually contains before a campaign goes out.

Try asking
Check the subscriber count for the 'VIP customers' segment in OneSignal before we schedule tonight's push.

Representative actions

  • Create or Update OneSignal User

    Registers a user or updates their subscriptions, used when onboarding or correcting a subscriber.

  • Delete User Alias

    Removes one alias from a user while keeping the rest of their identifiers in place.

  • Edit OneSignal Device

    Updates attributes on an existing device record once you have its player ID.

  • View OneSignal Segment

    Returns the subscriber count for a given segment, useful before sending a targeted campaign.

  • Update Subscription By Token

    Enables or disables a subscription using its token, for changes made outside the SDK.

Connection

API and auth details

OneSignal User Auth focuses on securely identifying users and verifying external IDs for customer-engagement workflows. Integrations can connect user identity, aliases, subscriptions, login/logout flows, tags, segments, and cross-channel messaging events while using documented OneSignal identity verification and API-key practices.

FAQ

Questions people ask before connecting OneSignal User Auth

Can Claude fix OneSignal subscriber issues?

Yes. With a OneSignal User Auth connection shared to a type.com Space, the agent can update users, aliases, and subscriptions directly from a thread.

How is OneSignal authenticated in type.com?

OneSignal User Auth uses an API key, added once by an admin when the connection is created and shared with specific Spaces.

Can segment checks run on a schedule?

Yes. A type.com automation can check a OneSignal segment's size on a recurring basis and post the count to a channel before a campaign.

Is this the same as a OneSignal User Auth MCP server?

Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.

More email & messaging connectors

All Email & Messaging integrations