# Expo Push with Notifly

Canonical page: https://notifly.io/integrations/expo
Last updated: 2026-10-02

An Expo access token and the Expo push tokens your app registers per subscriber. Each device gets its own send; malformed tokens are pruned.

## What you need from Expo Push

The fields the dashboard asks for when you connect Expo Push, from its Delivery Provider Credentials form:

| Field | Required | Stored | Notes |
| --- | --- | --- | --- |
| Access Token | Required | Encrypted at rest |  |

## Connect Expo Push in the dashboard

1. Sign in at https://app.notifly.io, open Integration Store in the sidebar and choose Connect Provider.
2. In the Connect Integration sheet, open the Push tab, find Expo Push and choose Connect.
3. Pick the environment the integration belongs to. Development and Production keep separate integrations.
4. Fill in Delivery Provider Credentials with the fields above, then choose Create Integration.

## Trigger a notification

```bash
curl -X POST https://api.notifly.io/v1/events/trigger \
  -H "Authorization: ApiKey $NOTIFLY_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"<workflow-id>","to":{"subscriberId":"<subscriber-id>"},"payload":{"body":"Hello from Notifly"}}'
```

## What Notifly adds around Expo Push

- Workflows around the send: One trigger runs a workflow: this provider’s step can sit beside in-app, email, SMS, push and chat steps, behind digest, delay and throttle steps.
- Subscriber preferences, enforced at send: Before each step runs, the subscriber’s workflow and channel preferences are checked; an opted-out step is skipped and the reason is recorded.
- An in-app Inbox next to it: The same workflow can write to the Notifly Inbox, a real-time in-app feed you embed with the React component or the JavaScript SDK.
- Per-trigger provider parameters: Anything the trigger passes under overrides.providers.<provider id> is merged into the request Notifly sends to the provider, per workflow or per step.
- Activity you can debug: Every message gets execution details in the activity feed, including the response or error the provider returned.
- Secrets encrypted at rest: API keys, tokens and service accounts are stored encrypted with AES-256; new and re-saved credentials use authenticated AES-256-GCM. The table above marks which of this provider’s fields that covers.

## More

The full guide, with provider-specific setup, code samples and answers to common questions: https://notifly.io/integrations/expo

All provider guides: https://notifly.io/integrations (markdown: https://notifly.io/integrations.md)