Skip to content
Recued
Menu
← Back to recipes

Create OneSignal segment intake

by recued-core v1

Approval-gated OneSignal segment creation workflow. It creates exactly one segment through recued-core.onesignal.segment.create using documented filter expressions. It never sends notifications, deletes segments, mutates users or subscriptions, exports reports, or calls arbitrary OneSignal APIs.

How it works 8 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (8 steps)
app_id_trim trim
Trim whitespace from setting app id
name_trim trim
Trim whitespace from setting name
reason_trim trim
Trim whitespace from setting reason
has_app compare
Check if app id trim has data
has_name compare
Check if name trim has data
ready all
Check if all conditions are true
create_segment ?
skip: step.ready not_equal true
card to_summary
Format results as a summary card
Settings 5 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

name setting =
app id setting =
reason setting =
filters setting = [object Object]
onesignal setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Onesignal connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

onesignal onesignalsegmentaudiencefilterstargetingapprovalpack:onesignal

Details

8 steps 5 configurable settings recipe_id: create-onesignal-segment-intake