Update OneSignal user properties
Approval-gated OneSignal user update workflow. It reads the current user and identity aliases, then updates properties or counters for exactly one user through recued-core.onesignal.user.update. It never creates users, creates subscriptions, sends notifications, deletes identity aliases, deletes users, exports data, or calls arbitrary OneSignal APIs.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (11 steps)
app_id_trim
trim
Trim whitespace from setting app id
alias_label_trim
trim
Trim whitespace from setting alias label
alias_id_trim
trim
Trim whitespace from setting alias id
reason_trim
trim
Trim whitespace from setting reason
has_app
compare
Check if app id trim has data
has_alias
compare
Check if alias id trim has data
ready
all
Check if all conditions are true
current_user
?
identity
?
update_user
?
skip: step.ready not_equal true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
app id
setting
=
deltas
setting
=
[object Object]
reason
setting
=
alias id
setting
=
onesignal
setting
=
properties
setting
=
[object Object]
alias label
setting
=
external_id
refresh device metadata
setting
=
false
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.