OneSignal is a customer engagement platform offering push notifications, email, SMS, and in-app messaging services.
OneSignal is a customer engagement platform offering push notifications, email, SMS, and in-app messaging services. On Nagent, OneSignal User Auth is exposed as a fully-configurable notifications integration that any agent can call — 12 actions, and API key authentication. No code is required to wire OneSignal User Auth into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use OneSignal User Auth to automate the kinds of tasks notifications teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire OneSignal User Auth into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against OneSignal User Auth, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ONESIGNAL_USER_AUTH_CREATE_USERTool to create a new user or modify the subscriptions associated with an existing user. Use when you need to register a user with OneSignal or update their subscriptions.
Input parameters
Your OneSignal App ID in UUID v4 format.
Defines identifiers for the user. The external_id must be used and should be unique across users.
User profile data including tags, preferences, and other properties.
The subscriptions object allows for creating or transferring subscriptions to a specified user.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONESIGNAL_USER_AUTH_DELETE_ALIASTool to remove an alias from a OneSignal user. Use when you need to delete a specific alias identifier from a user while preserving other aliases. The user is identified by one alias (alias_label/alias_id) and a different alias (alias_label_to_delete) is removed.
Input parameters
Your OneSignal App ID in UUID v4 format. See Keys & IDs documentation.
The specific identifier for the given alias to identify the user.
The alias name or key to locate the user. Most commonly set as 'external_id' but can be the 'onesignal_id' or a custom alias.
The name of the alias to remove from the user.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONESIGNAL_USER_AUTH_EDIT_DEVICETool to update an existing OneSignal device (player) record. Use when you have the player_id and need to modify device attributes.
Input parameters
Device latitude.
Version of the OneSignal SDK.
Device longitude.
Custom tags to set on the device.
Advertising identifier (IDFA or AAID).
OneSignal App ID the device belongs to.
Country code (e.g., 'US').
Locale code of the device (ISO 639-1).
Seconds the player has been online.
Offset in seconds from UTC (negative if behind).
Operating system version of the device.
Unique device (player) ID to update.
Unix timestamp when the device was created.
Push token (e.g., FCM or APNS token) or email.
Current iOS badge count displayed on the app icon.
Last active time as a Unix timestamp.
Total amount spent by the user.
Hardware model of the device.
App version of the device.
Number of times the app has been opened.
1 = subscribed, -2 = unsubscribed (iOS only).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONESIGNAL_USER_AUTH_ONESIGNAL_VIEW_SEGMENTTool to retrieve the subscriber count for a specific OneSignal segment. Use when you need to know how many subscribers are in a segment.
Input parameters
The OneSignal App ID to retrieve segment for.
The OneSignal Segment ID to retrieve details for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONESIGNAL_USER_AUTH_UPDATE_SUBSCRIPTION_BY_TOKENTool to update properties on an existing subscription using its token. Use when you need to enable or disable subscription status when managing outside of the OneSignal SDK.
Input parameters
The push token, email address, or phone number associated with the subscription. Format must match the token_type (e.g., valid email for Email type, E.164 format for SMS, 64-char hex for iOS).
Your OneSignal App ID in UUID v4 format.
The subscription channel type. Must match the format of the token.
The subscription properties to update.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONESIGNAL_USER_AUTH_VIEW_APPTool to retrieve details for a specific OneSignal app. Use after authenticating to inspect app settings.
Input parameters
The OneSignal App ID to retrieve details for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONESIGNAL_USER_AUTH_VIEW_BROADCASTSTool to view inbox broadcasts for a OneSignal app. Returns broadcasts in descending order of creation. Use when retrieving in-app messages or inbox content for an app.
Input parameters
The number of broadcasts to retrieve. Defaults to OneSignal default if omitted.
Your OneSignal App ID in UUID v4 format. See \[Keys & IDs\](/docs/keys-and-ids).
The exclusive lower bound of broadcasts to retrieve. Pass in successive requests to page through results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONESIGNAL_USER_AUTH_VIEW_DEVICETool to retrieve details for a specific device/player. Use when you have a player_id and optional app_id.
Input parameters
OneSignal App ID to scope the lookup. If omitted, uses the default app from authentication.
The OneSignal Player (device) ID to retrieve details for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONESIGNAL_USER_AUTH_VIEW_OUTCOMESTool to view all outcomes associated with a OneSignal app. Use to retrieve outcome metrics filtered by time range, platforms, and attribution type.
Input parameters
OneSignal App ID in UUID v4 format to retrieve outcomes for.
List of outcome names with aggregation type to fetch. Format: 'outcome_name.aggregation_type' (e.g., 'my_outcome.count' or 'my_outcome.sum'). For clicks use 'os__click.count', for confirmed deliveries use 'os__confirmed_delivery.count', for session duration use 'os__session_duration.count'.
Comma-separated list of platform device_type integers to include. Defaults to '0,1,2,5,8,11,14,17' if not specified.
Time range for outcome data.
Attribution type for outcomes.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONESIGNAL_USER_AUTH_VIEW_SEGMENTSTool to list all segments for an app. Use after obtaining the app_id to retrieve a paginated list of segments.
Input parameters
Number of segments to return (1 to 300). Defaults to OneSignal default if omitted.
OneSignal App ID to list segments for
Offset for pagination (number of items to skip).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONESIGNAL_USER_AUTH_VIEW_USERTool to retrieve user details by alias label and ID. Use when you need to fetch user data including tags, subscriptions, and identity information.
Input parameters
Your OneSignal App ID in UUID v4 format. See \[Keys & IDs\](/docs/keys-and-ids).
The specific identifier for the given alias to identify the user.
The alias name or key to locate the user. Most commonly set as `external_id` but can be the `onesignal_id` or a custom alias. See \[Aliases\](/docs/aliases).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONESIGNAL_USER_AUTH_VIEW_USER_UNREAD_MESSAGE_COUNTTool to retrieve the unread message count for a specific user. Use when you need to check how many unread inbox messages a user has.
Input parameters
Your OneSignal App ID in UUID v4 format. See \[Keys & IDs\](/docs/keys-and-ids).
The identifier or value set for the desired alias label.
The alias name or key to locate the user. Most commonly set as `external_id` but can be the `onesignal_id` or a custom alias.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 43 agents privately built on Nagent that already use OneSignal User Auth.
Build on Nagent
Connect OneSignal User Auth to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find OneSignal User Auth, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, OneSignal User Auth is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once OneSignal User Auth is connected, you configure its 12 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop OneSignal User Auth steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a OneSignal User Auth event fires, the agent kicks off automatically.
Every OneSignal User Auth action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While OneSignal User Auth ships with 12 pre-built notifications actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching OneSignal User Auth together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build OneSignal User Auth-based workflows tailored to your business.