OneSignal message operations digest
Scheduled read-only digest for OneSignal customer messaging operations. It reads recent notifications and legacy player/device records for one app through recued-core.onesignal, renders compact tables, and can send an in-app nudge when messaging records are visible. It never creates messages, cancels messages, creates segments, mutates users or subscriptions, deletes audience data, exports CSV/history reports, or calls arbitrary OneSignal APIs.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (15 steps)
app_id_trim
trim
Trim whitespace from setting app id
notifications_raw
?
players_raw
?
notifications
default
Apply default
players
default
Apply default
notification_count
count
Count items in notifications
player_count
count
Count items in players
visible_count
sum
Sum values in
has_records
compare
Check if visible count is greater than 0
notify_enabled
compare
Check if setting notify when records equals true
should_notify
all
Check if all conditions are true
notify
?
skip: step.should_notify not_equal true
notification_table
to_table
Format results as a data table
player_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
app id
setting
=
channels
setting
=
in_app
end hour
setting
=
10
weekdays
setting
=
1,2,3,4,5
onesignal
setting
=
row limit
setting
=
25
start hour
setting
=
8
notify when records
setting
=
true
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.