Connectors
Your services, connected once.
Add a service's public details, check the connection, and build with it in code or with Sanic AI. Your app talks to the service directly, with nothing passing through Appsanic.

How a connection works
Add it. Check it. Build with it.
Three steps, all inside the editor's Connectors panel.
Add the public details
Each connector asks for exactly what a client app may hold: a project address, a publishable key, an App ID. Private keys are refused.
Check the connection
A read-only check confirms the details work and lists what it found, such as your tables. It checks that one configuration, nothing more.
Build with it
Write against the typed
@appsanic/connectorsclient in Code, or ask Sanic AI. If a request needs a service you have not connected, Sanic AI asks you to connect it first.


The seven connectors
What each one includes, and what stays with the provider.
Every connector runs from the app itself with public configuration. Some features need a native build rather than the browser preview.
Supabase
Data and sign-inAccounts, a database, file storage and more, from your own Supabase project.
Set up Supabase- Included
- Database, sign-in and Storage
- Realtime and RPC
- Calls to your existing Edge Functions
- You enter
- Your project URL and its publishable key, for a Test and a Live project.
- Runs in
- Browser preview
- Expo Go
- Native build
Tables, access policies and functions are set up in Supabase. Appsanic never administers your project or runs migrations for it.
- Included
- Public posts and pages
- Categories
- Search
- You enter
- The address of a site with its public REST API available over HTTPS.
- Runs in
- Browser preview
- Expo Go
- Native build
Reading only. Writing or editing content from the app is not included.
Shopify (opens in a new tab)
StoresBrowse a store's products and collections inside your app.
Read the connector guide- Included
- Public products
- Product details
- Collections
- You enter
- Your store's address. Reads use no token at all.
- Runs in
- Browser preview
- Expo Go
- Native build
Checkout, orders and private tokens stay with Shopify. A purchase flow needs its own integration.
- Included
- Offerings and purchases
- Restore purchases
- Subscription entitlements
- You enter
- The public SDK keys for your app's platforms.
- Runs in
- Not in Browser preview
- Not in Expo Go
- Native build
Products, prices and store credentials are set up in RevenueCat. Purchases run only in a native build, never in the browser preview or Expo Go.
OneSignal
NotificationsLet people opt in to push notifications from your app.
Read the connector guide- Included
- Permission prompt
- Device subscription status
- Opt in and opt out
- You enter
- Your public App ID.
- Runs in
- Not in Browser preview
- Not in Expo Go
- Native build
Sending notifications and platform push setup happen in OneSignal. Needs a native build.
Algolia
SearchSearch the records you have indexed, with filters and suggestions.
Read the connector guide- Included
- Search and filters
- Pagination
- Facet suggestions
- You enter
- A search-only key that the editor checks really is search-only before it saves it.
- Runs in
- Browser preview
- Expo Go
- Native build
Indexing and administration stay in Algolia. No index is ever written from the app.
- Included
- Native error reporting
- Messages and breadcrumbs
- Flush before exit
- You enter
- Your public DSN.
- Runs in
- Not in Browser preview
- Not in Expo Go
- Native build
Source map uploads and private tokens are outside the connector. Needs a native build.
Boundaries worth knowing
Direct, public and yours.
Connectors are designed so that nothing private ever has to leave your provider accounts.
Public configuration only
The compiled app carries the same public details a website would. Your provider's own access rules protect the data, not secrecy.
Test and Live kept apart
Two saved configurations per connector. Switching changes previews and future builds, not an app that is already installed.
Keys never go in chat
Sanic AI sees connection status and what a service can do, never the values you entered. Requests for a missing service go through the editor.
A check is a check
A successful connection check proves that one configuration answers. Test the full flow in the preview and on a device before you ship.
Connect your first service in a free account.
Connectors are included on every plan, with the visual editor and the code workspace.

