Overview
The OneSignal + Materialize integration enables automatic syncing of custom events from your Materialize streaming database to OneSignal to trigger automated messaging campaigns and Journeys based on real-time user behavior. Materialize is a PostgreSQL-compatible streaming database that maintains incrementally updated views of your data, enabling real-time analytics and event processing.What data syncs
Data moves one way, from Materialize into OneSignal.
The Materialize integration does not create users or subscriptions, set Tags, or import audiences. OneSignal does not send message events to Materialize. To send message events to a system you control, use Event Streams. See what data each integration syncs to compare integrations.
Requirements
OneSignal
- A paid OneSignal plan. This integration isn’t available on the Free plan. See plans.
- If you import events, they become Custom Events. Custom Events follow your plan’s stored event allotment.
Materialize
- Materialize account with console access
- App Password for external tool authentication
- Materialized views or tables containing event data
- Event data accessible in your Materialize database
Setup
1
Get Materialize connection details
Sign in to the Materialize console and navigate to the Connect page to find your connection details.
2
Create App Password
In the Materialize console, create a new App Password for OneSignal to use for authentication.
3
Connect to OneSignal
In OneSignal, go to Data > Integrations and click Add Integration.Select Materialize and provide:
- Host: Your Materialize host name (found under External Tools in the Materialize console Connect page)
- Username: Your email address (used to sign in to Materialize)
- Password: The App Password created in Step 2
- Database: Database name (optional, defaults to
materialize)
4
Test connection
Click Test to verify the connection is working correctly.
Event data mapping
Map your Materialize view or table columns to OneSignal’s custom events format:The Sync Key is the column you designate as the unique identifier for each row during sync. OneSignal uses it to detect whether a row has already been processed, so re-syncing your data doesn’t create duplicate events. Choose a column with a unique text value per row. Don’t use a boolean or a value that repeats across rows.
Example Real-time Event View
Processing Modes
Materialized Views (Recommended)
Leverage Materialize’s real-time processing by syncing from materialized views that automatically update as new data arrives:SQL Query Mode
Write custom PostgreSQL-compatible queries to transform your event data:Real-time Stream Processing
Limitations
- Materialize only supports the Basic Sync Engine
- Real-time queries may consume more compute resources
- Complex joins across large datasets should be optimized
- Materialized views require ongoing cluster resources