Skip to main content
This guide explains the process of configuring and using Expo Push with Novu, from getting your credentials to sending your first notification.

How to configure Expo with Novu

Before you can send notifications, you must connect your Expo project to Novu by generating an access token and adding it to your integration settings.

Step 1: Generate your access token from Expo Push

Generate an access token from your dashboard. This token authorizes Novu to send notifications on behalf of your project.
1

Log in to Expo

Sign in at the Expo console.
2

Open Access Token

Navigate to the Credentials section in the project settings sidebar. Click Access Token.Create Expo token
3

Create a token

A menu appears.
4

Generate the token

Give it a descriptive name, and then click Generate New Token.Generate Expo token
5

Copy the token

Copy and save the generated access token. You need it in the next step.Copy Expo token

Step 2: Connect Expo Push to Novu

Next, add the access token to your Expo integration in the Novu dashboard.
1

Log in to the Novu dashboard

Open the Novu Dashboard.
2

Open Integration Store

On the Novu dashboard, navigate to the Integration Store.
3

Connect a provider

In the Integration Store, click Connect provider to begin setup.
4

Select Expo Push

In the Push tab, choose Expo Push from the provider list.
5

Paste the access token

In the Expo integration form, paste the access token that you copied from Expo into the Access Token field.Expo Integration in Novu
6

Create the integration

Review your credentials, then click Create Integration to save.

Using Expo Push with Novu

Once your integration is configured, you can start sending push notifications by registering your subscribers’ device tokens and triggering a workflow.

Step 1: Add subscriber device token

Before Novu can send a push notification to a subscriber (user), you must associate their device’s unique push token with their Novu subscriber profile. You can do this by making an API call to update the subscriber’s credentials.
Novu automatically removes invalid device tokens from a subscribers’ profile and then sends the failure details to the MESSAGE_FAILED webhook.

Step 2: Send a notification

Now you’re ready to send a push notification.

Configure Expo overrides

Save an Expo override on the Push step when you need Expo Push fields beyond the step subject and body — for example data, sound, priority, or ttl. The override is stored on the step, so it is versioned and promoted with the workflow, and every trigger sends it without changing your trigger call.
Provider content overrides in the workflow editor are rolling out gradually and may not be available on your Push step yet. Overrides passed at trigger time work regardless. See provider content overrides.
Expo overrides are validated against the Expo Push message request format. The editor autocompletes supported field names, validates the JSON, and flags unsupported fields.
  • to is managed by Novu. Novu fills device tokens from the subscriber’s credentials — do not set to in the override.
  • body falls back from the step. If your override omits body, Novu uses the rendered Push step body.
  • title is not seeded. Set title in the override when you want one; Novu does not copy the step subject automatically.
See the Expo Push message format for the full field list.

Using overrides to customize notifications