Xano Tips and Tricks
Setting up your App with Xano can be a bit different from what you are used to with Adalo Collections, so we've got you covered with some Tips and tricks on what you can expect!
Last updated
Was this helpful?
Setting up your App with Xano can be a bit different from what you are used to with Adalo Collections, so we've got you covered with some Tips and tricks on what you can expect!
Last updated
Was this helpful?
Skill Level: Expert
Ensure you have completed the Help Doc.
Have a Xano account and workspace setup. Follow to do so.
You must have a Team or Business Adalo plan to use this feature.
Make sure that when creating a new user you are meeting the Filters that you set up in Xano for each specific property.
Please make sure that the Base URL is for an API Group, it should look like this: https://x8kj-letl-tlmt.n7.xano.io/api:#####.
Custom domains for your Xano APIs are also supported.
Xano Collections are treated as (meaning that everything that is available for Ext. Collections is supported with Xano Collections).
When Signing-up your users please be aware that a “Create User” action is not going to Log in to your user, therefore Actions or filters applied to the "Logged in user" will not work. You can think of the Xano Sign Up action as a combination of creating a user and logging in all at once.
Xano only supports POST methods for Updates. Therefore whenever you are using a PUT or PATCH, those will get set to POST.
By default, Xano expects a full object to be sent in when doing Updates. This means that when you update a row in your Xano Collection, if there are any fields left empty in your Adalo Action, it will result in empty/null values in Xano. A way to avoid this will be to fill in all your Properties with by Current _____ > The corresponding property. You can also change this behavior in .
Please make sure that after you have made a change to your Xano APIs you are hitting the Publish Button. When you come back to Adalo, in order to see those changes reflected, you will have to hit on "Edit Settings" on the Specific "Collection" you changed.
It is important to note that when you have multiple “Update” endpoints for a collection (e.g. a PUT for full object updates and a PATCH for partial updates) we will pick the last one and set it to POST, and that's the one that will show for your Update action for that specific Collection. If you would like to change this, you can manually configure your endpoints by going to “Edit Settings” for that collection in Adalo.
There isn't a way of transitioning an App that is currently using Adalo Collections to use Xano Collections. You'll have to create a New App and use the Xano Collections option with it.
Adalo will not be directly showing Xano Errors, for instance, if your Adalo Actions stop working because you reached your Xano Plan limits, you will be notified about it in your e-mail.
When seeing "Sign-up failed" or "Action cannot be completed" errors we will highly recommend you open your Dev tools in your Browser > Network > Click on the request that failed that will be highlighted in Red and that will help guide you on what's the Error that's causing your Action to fail.
After you have created an App using Xano Collections you will be able to use but you won't be able to use Adalo Collections for that specific App.
You'll be able to use our and components. Please keep in mind that you cannot have pagination turned on for the GET ALL for your Users collection.
When using the component, you need to have “Name” as an optional param on your /auth/signup endpoint.
Adalo Push Notifications Actions will work the same way they work for Adalo Collections. You can learn more about how to set these up in our .
Sending must use the User ID.
Collection Permissions must be set on Xano's end. will not work with Xano Collections.
will continue working the same way they currently do for Adalo.
In addition to our existing , here are some tips that you could use to troubleshoot your App, in addition to our :
A good first step for troubleshooting your App when working with Xano is to try to recreate the action you are trying to perform in Adalo in and check if you are receiving an Error there.
We use the on Xano as a reference for what you will be seeing in Adalo. We will recommend you use it in Xano to troubleshoot issues that you are facing with your APIs.
As Xano will be storing your information GDPR Compliance will be managed by Xano. You can read more about how they manage this in their .
As with all integrations, Adalo is only able to provide support for the Adalo side of the integration. For assistance with your Xano account, dashboard, or implementation, please use the Xano , Xano , , or contact directly.
If you need additional help with this article, you can always ask in our! Be sure to paste the link to this article in your post as well! We also have a that you may find helpful!
Do you have a tutorial or help doc request?