Xano integration – editor fetching endpoints from wrong branch

Hi everyone,

We’re experiencing an issue with the Xano integration in WeWeb.

We use three Xano branches: development, acceptance and production. We’ve configured the Xano integration in WeWeb to use the corresponding branches for each environment.

However, the WeWeb editor is fetching the API endpoints as they exist in the production branch, instead of the development branch. This means changes to endpoints in our development branch aren’t reflected in the WeWeb editor.

I’ve recorded a Loom video demonstrating the issue:

My question is: How can we configure the Xano integration so that the WeWeb editor retrieves the API endpoint definitions from the development branch rather than production? We need to be able to work with new or modified endpoints in development without first merging those changes into production.

Is this supported by the integration, or is there a workaround?

I already raised this issue through WeWeb’s support chat yesterday and followed up today, but unfortunately haven’t received a response yet. So I’m hoping someone here can point me in the right direction.

Thanks in advance!