Expo Push
Push notifications come in two halves: an app that can receive them, and a server that sends them. The agent can generate both halves, but remote receipt still needs platform credentials, native configuration, and a development build. This connector validates an Expo access token for build planning; it is not a runtime credential delivery service.
You connect Expo Push when your app needs to send notifications that aren't triggered by the user. A new message arrived, an order was dispatched, a reminder is due. Anything where your backend decides it is time to notify someone.
What you get by connecting it
With the connector in place, the agent can:
- Validate and encrypt a project-scoped Expo access token without exposing it to the model or browser.
- Generate a server endpoint or scheduled-job contract that sends through Expo after you deploy it and provision a separate runtime token.
- Generate registration, permission, storage, and tap-through code plus the native-development-build checklist.
The receiving code does not need the connector's secret, but it still depends on native build credentials and a real-device development build. Expo Go is not a substitute for Android remote-push testing on SDK 53 and later.
Connecting it
You need one credential: an Expo access token.
- Go to expo.dev and sign in to your account.
- Open your account settings and find Access Tokens.
- Create a new access token and copy the value. Expo only shows it once, so copy it before you close the dialog.
- Open the project build, select Connectors, choose Expo Push, and enter it. The connection applies only to that project.
Connecting requires a paid plan. Saved secrets are shown as dots, never the value, so browser JavaScript can see that a token exists without receiving it. Use Test now to re-check the saved token against Expo and Disconnect to remove it from the project.
Connector OAuth is not currently available. Enter the access token in the project's connector form.
Keys and security
An Expo access token is a secret. Anyone holding it can send pushes on your behalf, so it must never be bundled into an app people download.
That puts Expo Push in the secret key plus relay tier. The generated app never carries a token. The agent can generate a relay such as a Supabase Edge Function, but you must deploy it and add a separate Expo token directly to that runtime's secret manager. The saved connector token is never copied there.
Managed connector secrets are encrypted at rest with AES-256-GCM. The model prompt never receives the decrypted token, and the agent will never ask you for it in chat. See Connectors Overview for the build-time/runtime boundary.
Useful links
- Expo's own documentation: https://docs.expo.dev/push-notifications/overview/
- The Appsanic guide to the full notifications flow: Push Notifications
Next
Read Push Notifications for the end-to-end picture: registering devices, asking for permission the right way, and what the agent builds on both the sending and receiving sides.