Create the Event Stream
OneSignal delivers events through an Event Stream you configure in the dashboard. There is no API for creating one, so this is done by hand. Configure a single stream pointed at your StackOne Native Webhook URL.
The Native Webhook URL is generated once an account has been linked. You will paste it into OneSignal in a later step.
- Open the linked account in StackOne.
- Copy the value from Native Webhook URL.
Open the OneSignal dashboard and sign in with the account whose API key you connected to StackOne. Enter your Email and Password on the Log in to Your Account screen, then click Log in with Email.
Select the app you connected to StackOne, then click Event streams under Data in the sidebar. Click New Event Stream in the top right.
- The page lists existing streams by Name, Status, Created, Last activated and Destination URL, with All, Active, Inactive and Disabled tabs above them.
Type a name you will recognise later into Event Stream Name, for example `StackOne`. Under Event Selection, click Select Events.
- Free plans allow one active Event Stream. If you already have one, OneSignal shows You’ve reached the limit of 1 active Event Streams and you must set the existing stream inactive or upgrade before activating another.
The Select an event dialog groups every event by channel — In-App Message, Push Notification, Email, SMS and Live Activity — and shows each event's payload name beneath it. Tick the events you want delivered, then click Done.
- Select All ticks every event your plan allows; Clear All empties the selection.
- Events your plan cannot receive are greyed out with a padlock.
- Each event counts toward your plan's message-event volume. A single send to 100,000 users produces 100,000 delivery events on its own, so select only what you need.
- Apply Filters on the previous screen narrows a stream to specific messages or templates instead of all traffic.
Under Configure, leave Method on `POST` and paste your Native Webhook URL into URL. Under Headers, enter `Content-Type` as the Key and `application/json` as the Value.
- The Content-Type header is required. OneSignal sends no content type of its own, and without it StackOne cannot parse the body — every delivery fails with a 500.
- No authentication header is needed. StackOne authenticates the delivery using the token already in the Native Webhook URL.
- Add Header adds further rows if you need them.
Under Body, set the dropdown to Custom Body and paste this template exactly. OneSignal fills the Liquid placeholders in at delivery time, and these key names are what the connector's event routing reads.
- Paste it as written. The keys are flat and underscored on purpose — OneSignal's documentation shows a form with dotted keys like `"event.kind"`, which cannot be routed.
- Adding extra fields is safe. Removing `event_kind`, `message_id` or `event_timestamp` is not — routing, record ids and event times come from those three.
- ```json theme={null} { "event_id": "{{ event.id }}", "event_kind": "{{ event.kind }}", "event_timestamp": "{{ event.timestamp }}", "onesignal_id": "{{ event.onesignal_id }}", "external_id": "{{ event.external_id }}", "app_id": "{{ event.app_id }}", "subscription_id": "{{ event.subscription_id }}", "message_id": "{{ message.id }}" } ```
Click Send Test to post a sample request, then Save to keep the configuration and Activate to start delivering live events.
