ActionOneSignalUpdated September 2026

How do I list OneSignal notifications?

Short answer: You can list onesignal notifications in OneSignal by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the OneSignal List OneSignal Notifications action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List OneSignal Notifications in OneSignal — start free All 4 OneSignal actions

List OneSignal Notifications in OneSignal — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Limit limit	string	Optional	–

Sample request

{
  "limit": "{{trigger.limit}}"
}

Returns

{
  "total_count": 1,
  "notifications": [
    {
      "id": "abc",
      "failed": 5,
      "headings": {
        "en": "Hi"
      },
      "successful": 1000
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for List OneSignal Notifications.

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 List OneSignal Notifications.

What does the List OneSignal Notifications action do in OneSignal?

Paginated recent sends with delivery stats. For "which notifications got the most engagement" analysis.

What inputs does List OneSignal Notifications require?

List OneSignal Notifications 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 run history shows the failed step with its input and the error message OneSignal returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List OneSignal Notifications support batch operations?

Run List OneSignal Notifications inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within OneSignal's rate limits.

More actions

Other OneSignal actions.

Action

Get OneSignal App Statistics

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

Action

Send Push Notification

Sends a push to a specified audience — user IDs, segments, or in-call filter rules. The base hook for "external event → push to mobile users matching X criteria" workflows.

Action

Create OneSignal Notification

Alias for Send Push Notification — creates a push send. For external-event-driven push workflows.

List OneSignal Notifications in OneSignal — start free