In your Databricks workspace, click your username in the top bar and select Settings.
2
Navigate to Developer section
Click Developer.
3
Manage tokens
Next to Access tokens, click Manage.
4
Generate new token
Click Generate new token.
5
Configure token
Enter a comment like “OneSignal Integration” to help identify this token
Set the token’s lifetime in days (check your workspace documentation for maximum allowed duration)
Click Generate
6
Save the token
Copy the displayed token to a secure location, then click Done.
Save the token securely and don’t share it. If you lose it, you must create a new token. Tokens that remain unused for 90 days are automatically revoked by Databricks.
Recommendation: If you’re using PrivateLink or want the simplest setup, choose Personal Access Token. For direct connections with existing OAuth infrastructure, OAuth M2M works well.
Initial data sync can take 15–30 minutes to appear in BigQuery.While you wait, send messages via push, email, in-app, or SMS to trigger the events selected.
Syncs after saving/activating may take an additional 15-30 minutes to complete.
Deactivating may still result in one final sync after deactivation.
To ensure efficient data synchronization, our system automatically creates and manages staging datasets. These datasets, named with a pattern like fivetran_{two random words}_staging, temporarily store data during processing before it’s integrated into your main schema. These staging datasets are essential for maintaining a streamlined workflow and should not be deleted, as they will be automatically recreated.
Databricks workspace with SQL Warehouse or compute cluster
Personal Access Token with appropriate permissions
Event data tables containing behavioral data in Delta Lake format
Unity Catalog (recommended for data governance)
Setup Steps
1
Create Databricks Personal Access Token
Generate a Personal Access Token for OneSignal to access your Databricks workspace:
Navigate to User Settings in your Databricks workspace
Click Developer tab and then Access tokens
Click Generate new token
Enter a comment like “OneSignal Integration” and set expiration (recommend 90 days)
Save the generated token (you’ll need this for OneSignal)
2
Configure SQL Warehouse access
Ensure OneSignal can query your event data via SQL Warehouse:
Navigate to SQL Warehouses in your Databricks workspace
Select or create a SQL Warehouse for OneSignal access
Note the Server Hostname and HTTP Path from the connection details
Ensure the warehouse has access to your event data tables
3
Grant table permissions
Grant OneSignal read access to tables containing event data:
-- For Unity Catalog enabled workspacesGRANT SELECT ON TABLE catalog.schema.event_table TO `onesignal@yourdomain.com`;-- For Hive metastore tablesGRANT SELECT ON TABLE database.event_table TO `onesignal@yourdomain.com`;
4
Add integration in OneSignal
In OneSignal, go to Data > Integrations and click Add Integration.Select Databricks and provide:
Server Hostname: Your Databricks SQL Warehouse hostname
HTTP Path: SQL Warehouse HTTP path
Personal Access Token: Token created in step 1
Catalog (optional): Unity Catalog name if using Unity Catalog
5
Configure event data source
Specify the Databricks table containing your event data:
Database/Schema: Database or schema name containing event tables
Table: Table name with event records (e.g., user_events)
Event Query: Optional SQL query to filter or transform event data
Your event table should contain columns for:
Event name/type (String)
User identifier (String)
Event timestamp (Timestamp)
Additional event properties
6
Test the connection
Click Test Connection to verify OneSignal can access your Databricks workspace and read event data.
