Create OneSignal message intake
Approval-gated OneSignal message creation workflow. It reads recent notification context, then creates exactly one push, email, or SMS notification through recued-core.onesignal.notification.create using explicit app, audience, and message fields. It never creates segments, mutates users or subscriptions, cancels existing notifications, exports history, deletes records, 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
template_id_trim
trim
Trim whitespace from setting template id
url_trim
trim
Trim whitespace from setting url
send_after_trim
trim
Trim whitespace from setting send after
reason_trim
trim
Trim whitespace from setting reason
has_app
compare
Check if app id trim has data
recent_notifications
?
create_notification
?
skip: step.has_app not_equal true
recent
default
Apply default
recent_count
count
Count items in recent
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
url
setting
=
data
setting
=
[object Object]
app id
setting
=
reason
setting
=
contents
setting
=
[object Object]
headings
setting
=
[object Object]
onesignal
setting
=
send after
setting
=
custom data
setting
=
[object Object]
template id
setting
=
target channel
setting
=
push
include aliases
setting
=
[object Object]
excluded segments
setting
=
included segments
setting
=
Subscribed Users
include external user ids
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.