ActionOneSignalUpdated May 2026

How do I get OneSignal subscriber stats?

Short answer: Drop the "OneSignal → Get OneSignal App Statistics" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 4 OneSignal actions

Sample request

{}

Returns

{
  "id": "abc",
  "name": "My App",
  "players": 12000,
  "messageable_players": 10500
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get OneSignal App Statistics.

Any of these apps can fire this action as part of a workflow.

Google Sheets → OneSignal

2 Google Sheets triggers

HubSpot → OneSignal

18 HubSpot triggers

FAQ

Questions about Get OneSignal App Statistics.

What does the Get OneSignal App Statistics action do in OneSignal?

Returns subscribed-user count by platform and recent send aggregates. For "weekly push performance digest" rollup workflows.

What inputs does Get OneSignal App Statistics require?

Get OneSignal App Statistics has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if OneSignal returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get OneSignal App Statistics support batch operations?

Yes. Run Get OneSignal App Statistics inside a Loop node to process arrays. Tiny Command handles OneSignal's rate limits automatically so you don't have to throttle manually.

More actions