Onesignal to Redash Integration

How Datrise loads Onesignal into Redash

Datrise syncs Onesignal's notifications, subscribers, segments, apps, delivery events, and outcomes into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.

Ideal for lightweight, query-driven dashboards.

Endpoints

Onesignal: Push, in-app, and email message delivery.

Redash: Open-source SQL client for queries, visualizations, and dashboards.

How Onesignal entities map to Redash

Onesignal entity	Redash object	Notes
notifications	`onesignal_notifications`	id PK · custom fields → flattened columns for query results
subscribers	`onesignal_subscribers`	id PK · linked to onesignal_notifications
segments	`onesignal_segments`	id PK · linked to onesignal_notifications
apps	`onesignal_apps`	id PK · linked to onesignal_notifications

FAQ

How does Datrise handle Onesignal's custom fields in Redash?

Flexible values are stored as flattened columns for query results, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Redash types.

How does the Onesignal to Redash sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Onesignal to Redash the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.