---
title: "OneSignal Connector"
description: "Implementation notes for building and operating the OneSignal connector in Tajo."
url: https://tajo.io/docs/connectors/onesignal/
markdown: https://tajo.io/docs/connectors/onesignal.md
lang: en-US
robots: noindex
---

# OneSignal Connector

Connector status: In progress Being built. Not verified yet.

| 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` |

Connector implementation

## Build the OneSignal integration

Multi-channel customer messaging platform for push, email, SMS, and in-app messages

Omnichannel Engagement

*OneSignal connector flow from source system to Tajo mapping and Brevo activation.*

## Implementation Overview

**Build target**

Implement an OneSignal connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.

**Current status**

Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.

**Primary surface**

github.com/OneSignal/api

| Property | Value |
| --- | --- |
| Integration surface | OpenAPI |
| Status | In progress |
| Category | Omnichannel Engagement |
| Setup complexity | medium |
| Vendor documentation | [documentation.onesignal.com/reference/rest-api-overview](https://documentation.onesignal.com/reference/rest-api-overview) |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | [github.com/OneSignal/api](https://github.com/OneSignal/api) |
| MCP server | Not recorded |
| Last researched | 2026-04-12 |

Official OpenAPI specs repo drives all SDKs.

## Authentication

- Use [github.com/OneSignal/api](https://github.com/OneSignal/api) to generate or validate typed API clients and request models.
- Keep [documentation.onesignal.com/reference/rest-api-overview](https://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

No typed contract exists for OneSignal, so the direction of each resource and its conflict handling are not recorded. Direction is declared per resource on a connector contract; see the [connector catalog](https://tajo.io/docs/connectors) for how contracts are promoted.

## Mapping To Tajo/Brevo

No Brevo projection is recorded for OneSignal. A projection is declared on a typed connector contract, and OneSignal does not have one yet, so this page will not state a mapping it cannot source.

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](https://tajo.io/docs/connectors).

## Sources

- [Vendor documentation](https://documentation.onesignal.com/reference/rest-api-overview)
- [OpenAPI or schema source](https://github.com/OneSignal/api)
- [documentation.onesignal.com/docs/en/server-sdk-reference](https://documentation.onesignal.com/docs/en/server-sdk-reference)