OneSignal Strawberry

Devices checked against notifications, in one pass

It reads every device your OneSignal (REST API) account holds, drafts the changes that follow, and hands you a card for each one before a single device moves.

Open the device. Check it against something else. Write the change. Move to the next one. That is the OneSignal (REST API) afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a device until you approve it.

What it can do is exactly what OneSignal (REST API) exposes to an account you authorise and nothing beyond it: 4 operations, 2 reads and 2 writes. In practice that means it can create a notification and add a device, and work across the devices and notifications.

The OneSignal (REST API) API stops at OneSignal (REST API). A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.

Can it get devices on its own?

2 of the 4 operations are reads. Your account, not a guess at it: a companion can get devices and get a device, and the full list below is the whole list, with nothing inferred from OneSignal (REST API)'s documentation.

The devices are what most of this inventory is about, alongside the notifications. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of OneSignal (REST API) admin becomes a queue you review.

  • Get Devices
  • Get Device

Which devices wait for your approval?

All 2 write operations wait for you. A companion can create a notification and add a device, and each one is staged on an approval card first: you see the device, the field and the new value before it lands in OneSignal (REST API).

Nothing in OneSignal (REST API) is sent, changed or deleted on your behalf without that click, and a rejected card leaves the device exactly as it was. The gate is the same one on every surface, described at security.

  • Create Notification
  • Add Device

Can it create notification on a schedule?

Yes. Saved as a routine, the OneSignal (REST API) devices pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.

The sales pipeline playbook catalogues the other recurring shapes of pipeline work, the OneSignal (REST API) devices sweep among them, and finished runs are published at real runs.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. Connect your OneSignal (REST API) account and a companion works 4 operations in it, with every change staged for your approval. You authorise the connection yourself and the credential is held encrypted where Strawberry never receives it.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide