🧩 Xano integration updates

Throughout the summer, we released a number of updates to improve our Xano plugins and support the latest Xano features like data sources and branches.

You can now:

• connect your Xano projects using Xano's Metadata API and access tokens,
• add the custom domain of your Xano instance (if you have one),
• add custom headers at plugin, collection level, and action level,
• enable a passwordless login without resorting to code thanks to the "Store auth token" no-code action.

In addition, both Xano plugins now support Xano data sources and branches. 

Xano data sources and branches in WeWeb

In WeWeb, you can now decide to work with different Xano data sources and branches depending on whether you're working:

• inside the WeWeb editor,
• on the app published in the WeWeb staging environment, or
• on the published app in production.

This is helpful if you want to iterate on your WeWeb app with test data and API calls that are still in editing mode in Xano without breaking your live app.

For example, you could have a "live" data source and a "test" data source in Xano:

‍

In the example below, we chose to work with the data from the "test" data source inside the WeWeb editor, and on the app in staging:

‍

As a result, when working in the WeWeb editor or viewing the app published in staging, the data that is displayed will be the data from the "test" data source in Xano. We will not be able to see or work with the data in the "live" data source.

We can apply the same logic to work with different Xano branches. In the example below, we will test the Xano "v2" branch in the WeWeb editor and the app we publish on the staging environment but the Xano "v1" branch will still be live in our app in production:

‍

Note that Xano data sources and branches are advanced features that may require some time to master if you don't have a developer background. We think the power and flexibility it gives you to build professional web-apps is well worth the trouble though.

Learn more about working with different Xano data sources and branches in WeWeb.

‍

Other Xano improvements & fixes

In addition to the new features described above, the team took the opportunity to make some UX improvements and bug fixes related to the Xano plugins:

‍

• Xano base domain: we now store the Xano base domain when you select your instance, so if you upgrade your Xano instance and the base domain changes, you will now be able to select it again and every already configured will use the new base domain with no further required action on your part. 

‍

• Social login fix: when you cancel a social login (e.g. by clicking on the back button of the Google login page), we don’t try to continue the login anymore.

‍

• Input validation: we now recognize the data type Xano expects when you are using Xano plugins and will display a warning in the WeWeb editor when you try to bind an input to another data type.

In the example below, I tried to bind an integer to a field that expects a string in Xano. As a result, I can see an "Expected format" warning: