OneSignal Connector
Connector status: In progress Being built. Not verified yet.
Illustration · sample data
Sync example
Source
OneSignal
Connector status: In progress
Destination
Your other tool
Connector status: Custom tool
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
record.id | source_id | record_1042 |
record.updated_at | updated_at | 2026-10-18T08:00:00Z |
record.value | value | sample_value |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
Connector implementation
Build the OneSignal integration
Multi-channel customer messaging platform for push, email, SMS, and in-app messages
Implementation Overview
Implement an OneSignal connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.
Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.
raw.githubusercontent.com/OneSignal/api/main/api.json
| Property | Value |
|---|---|
| Integration surface | OpenAPI |
| Status | In progress |
| Category | Omnichannel Engagement |
| Setup complexity | medium |
| Vendor documentation | documentation.onesignal.com/reference/rest-api-overview |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | raw.githubusercontent.com/OneSignal/api/main/api.json |
| MCP server | Not recorded |
| Last researched | 2026-10-15 |
Official OpenAPI document (version 1.2.2) in OneSignal’s api repository, which drives all SDKs. The document still names the legacy host onesignal.com/api/v1; keys since November 2024 use api.onesignal.com with Authorization: Key.
Authentication
-
Use raw.githubusercontent.com/OneSignal/api/main/api.json to generate or validate typed API clients and request models.
-
Keep documentation.onesignal.com/reference/rest-api-overview linked from the connector runbook so operators can confirm vendor behavior during incidents.
-
Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
-
Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.
Data To Sync
Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:
- Contact and identity records
- Campaign, messaging, or audience state
The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.
Sync Shape
| Resource | Direction | Conflict handling |
|---|---|---|
subscriptions | bidirectional | source_wins, loop guard none |
OneSignal is the record of the subscription and its status; the writes back (upsert_user, update_user_tags) are keyed on the external id and converge, and the full read has no watermark a write could move.
Mapping To Tajo/Brevo
subscriptions → Brevo contact
Requires: workspace api key.
| Source field | Brevo destination | Via | Note |
|---|---|---|---|
email | email | — | |
firstName | attributes.FIRSTNAME | — | |
lastName | attributes.LASTNAME | — | |
id | attributes.ONESIGNAL_ID | — | |
externalUserId | attributes.ONESIGNAL_EXTERNAL_USER_ID | — | |
createdAt | attributes.ONESIGNAL_CREATED_AT | — | |
tajo_email_marketing_consent | filter | — | the canonical consent pair, derived from the email subscription’s status; a push or SMS record never passes |
The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the connector catalog.