DatriseAI-first ETL

Source connector

Onesignal connector

Onesignal integration for databases, warehouses and BI tools

Push, in-app, and email message delivery. Datrise captures Onesignal entities such as notifications, subscribers, segments, apps, delivery events and outcomes, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `onesignal_notifications`) with a schema derived from the Onesignal API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Onesignal pipeline page, and join the waitlist to get the Onesignal connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Onesignal data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

ObjectLanding tableSync mode
notificationsonesignal_notificationsUpsert by primary key, incremental on updated-at
subscribersonesignal_subscribersUpsert by primary key, incremental on updated-at
segmentsonesignal_segmentsUpsert by primary key, incremental on updated-at
appsonesignal_appsUpsert by primary key, incremental on updated-at
delivery eventsonesignal_delivery_eventsAppend-only, incremental by timestamp
outcomesonesignal_outcomesUpsert by primary key, incremental on updated-at

Popular destinations for Onesignal

Choose a destination below to open the ready pipeline page.

  • A
    Airtable

    Relational spreadsheet destination for ops and go-to-market teams.

    View pipeline
  • A
    Amazon Athena

    Serverless SQL over S3 data lake tables.

    View pipeline
  • A
    Amazon DynamoDB

    Serverless key-value and document store on AWS.

    View pipeline
  • A
    Amazon QuickSight

    AWS serverless BI with SPICE and embedded analytics.

    View pipeline
  • A
    Amazon Redshift

    AWS petabyte-scale warehouse with Spectrum.

    View pipeline
  • A
    Amazon S3 Data Lake

    Object storage landing zone for parquet and snapshots.

    View pipeline
  • A
    Apache Superset

    Open-source BI for SQL exploration, charts, and dashboard publishing.

    View pipeline
  • A
    Azure Data Lake Storage

    ADLS Gen2 object storage for analytics workloads.

    View pipeline
  • A
    Azure Synapse

    Microsoft analytics workspace with SQL pools.

    View pipeline

Onesignal connector FAQ

What Onesignal data does the connector extract?
6 objects: notifications, subscribers, segments, apps, delivery events and outcomes. Each lands in its own table with types preserved; history-style objects (1: delivery events) load as append-only streams.
Is the Onesignal integration incremental?
Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Onesignal data?
Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Onesignal → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Onesignal pipeline with guided onboarding

Join the waitlist to get priority access for Onesignal integrations with guided setup, schema-aware mapping, and production-grade incremental sync.