Why Xano Is the Go-To External Database for Adalo
Adalo's built-in database works for small apps, but it degrades past 2,000–5,000 records per collection. Xano solves this by acting as a powerful backend-as-a-service: you build database tables, API endpoints, and business logic in Xano, then connect Adalo as a front-end client via External Collections.
The integration is powerful - but the setup has sharp edges that the documentation glosses over. As certified Adalo Experts, we've built and debugged dozens of Adalo+Xano architectures. This guide covers every pitfall.
Step-by-Step Integration Setup
Step 1: Prepare Xano Endpoints
Before touching Adalo, build your complete CRUD API in Xano:
- GET /items - Returns all records (paginated)
- GET /items/{id} - Returns a single record
- POST /items - Creates a new record
- PATCH /items/{id} - Updates a record
- DELETE /items/{id} - Deletes a record
Also create authentication endpoints if using Xano auth: POST /auth/login and POST /auth/signup.
Step 2: Get Your API Base URL
In Xano, navigate to your API group and copy the base URL. It follows this format:
https://x8kj-letl-tlmt.n7.xano.io/api:####Critical: This must be the API Group URL, not the individual endpoint URL. Adalo auto-discovers endpoints from the group.
Step 3: Connect in Adalo
In Adalo → Database → External Collections → Add Collection. Paste the Xano API base URL. Adalo will attempt to auto-detect your endpoints.
Plan requirement: External Collections require Adalo's Team or Business plan. Starter and Pro plans do not support this feature.
Top 5 Integration Failures
1. Login Works in Xano, Fails in Adalo
Cause: Adalo expects a specific response format from login endpoints: a token field at the top level and user data inside a user object. If your Xano response doesn't match this structure, Adalo silently fails.
Fix: In Xano, structure your login response as: {"token": "jwt_here", "user": {"id": 1, "email": "..."}}. make sure the email and password field names in Adalo exactly match the input names in your Xano endpoint.
2. External Collection Shows No Data
Cause: Your GET endpoint returns an object wrapping an array instead of a raw array. Adalo expects the root response to be an array of objects.
Fix: In Xano, make sure your GET All endpoint returns a direct array: [{"id": 1, ...}, {"id": 2, ...}], not {"data": [{...}]}. Adjust the Response filter in your Xano function stack if needed.
3. Update Operations Send Null Values
Cause: Xano expects the full object for updates. If an Adalo form only sends the changed fields, all others are set to null.
Fix: In your Xano PATCH endpoint, add conditional logic: only update fields that are present in the request body. Use Xano's Conditional filter to check if each field is not null before updating.
4. Relationships Between External Collections Don't Work
Cause: Adalo does not support direct relationships between External Collections. You can't link two Xano tables the way you link two native Adalo collections.
Fix: Pass filter parameters from your Adalo list to the Xano endpoint. For example, when a user taps an Order, navigate to a detail screen and pass the orderId. On the detail screen, call a Xano endpoint filtered by that ID.
5. Can't Switch Existing App to Xano
Cause: Adalo does not allow transitioning an app that already uses native Adalo Collections to use Xano Collections. This is a platform limitation, not a bug.
Fix: Create a new Adalo app with the Xano option enabled from the start. Migrate your data from the old app's database to Xano, then rebuild screens pointing to the new External Collections.
Performance Comparison
| Metric | Adalo Native DB | Adalo + Xano |
|---|---|---|
| Record limit comfort zone | Under 2,000 | 100,000+ |
| Query speed (filtered list) | Client-side filtering | Server-side filtering |
| Complex business logic | Not supported | Full server-side logic |
| Cost (monthly) | Included in plan | Xano: $0–$85/mo additional |
| Authentication | Built-in | JWT-based via Xano |
When to Skip Xano and Go Custom
Xano solves Adalo's database limitations, but it doesn't fix Adalo's front-end limitations: webview rendering, limited custom components, no code export. If you need both a powerful backend AND a native mobile experience, a custom build delivers better ROI.
Rehost handles full-stack migrations - from Adalo+Xano to React Native + custom API. We preserve your data and recreate your business logic. Get a free migration assessment →
FAQ
Do I need a paid Adalo plan for Xano integration?
Yes. External Collections require Adalo's Team or Business plan. Starter and Pro plans do not support external database connections.
Can multiple Adalo apps share the same Xano database?
Yes, but each Adalo app counts separately toward your plan limits. They don't share published status or settings.
Is Xano better than Supabase for Adalo?
Xano has deeper Adalo integration with auto-discovery of endpoints. Supabase requires more manual configuration. For Adalo specifically, Xano is the easier choice. For FlutterFlow, Supabase is often preferred.