# New Xano integration (WeWeb Unify) is not working well **URL:** \ **Category:** Ask us anything\ **Tags:** binding, xano\ **Created:** [May 12, 2026, 4:38pm UTC](https://community.weweb.io/t/new-xano-integration-weweb-unify-is-not-working-well/21194 "2026-05-12T16:38:10Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![hotwheels](https://avatars.discourse-cdn.com/v4/letter/h/3ab097/32.png) [@hotwheels](https://community.weweb.io/u/hotwheels)\ **Post date:** [May 12, 2026, 4:38pm UTC](https://community.weweb.io/t/new-xano-integration-weweb-unify-is-not-working-well/21194/1 "2026-05-12T16:38:10Z")
Since the WeWeb Unify was launched, I’ve been looking to migrate my current workflows from using the Xano plugins (which exposes data on the frontend) to the Xano integration. Unfortunately, I’ve been struggling with it / it’s been poorly designed. Here’s the state of things: **What’s working** 1. I have successfully set up the Xano integration with Authentication enabled. 2. I can only use the “API Request” action of the integration. **What’s not working:** 1. I can’t bind variables to an API endpoint. In **Image #1** , you can see there’s no way to bind the parameters individually (like we can for Collections or for the “API request” action of the Xano integration; it seems you can only bind the inputs as one JSON. So I tried to create a big JSON input but I couldn’t find the variables to bind the variables in the JSON to ( **see** **Image #2** in comments\*\*)\*\*. The variables just don’t appear. I’m a new user in this Community so I can only include one picture. 2. I can’t create the equivalent of Collections scoped to just the data I want to surface, using the Xano integration because there is no way to bind the parameters to variables ( **see Image 3 in comments** ). I contacted Support and their response was that I should use a GET all to pull all the data from the Xano database table, and then use filters to get the desired view. As it stands, the Xano integration is not usable and the [@weweb-team](https://community.weweb.io/groups/weweb-team) should look into this. If it’s just me not knowing how to use it, I’m open to learning. It’s already a lot of work replacing the Xano plugin with the Xano integration and these issues make them much harder and undermine trust in the quaity of the experience built. **Image** #1 ![Screenshot 2026-05-12 at 3.51.01 PM](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/7/c/7cd249b4aa1caab61864705379859864efe176e7.png) ---
**Author:** ![hotwheels](https://avatars.discourse-cdn.com/v4/letter/h/3ab097/32.png) [@hotwheels](https://community.weweb.io/u/hotwheels)\ **Post date:** [May 12, 2026, 4:54pm UTC](https://community.weweb.io/t/new-xano-integration-weweb-unify-is-not-working-well/21194/2 "2026-05-12T16:54:07Z")
Here’s image 2 and 3. I couldn’t include them in the main post **Image** #2: The variables and data are not visible/available in API Endpoints so you can’t bind anything. ![Screenshot 2026-05-12 at 3.52.05 PM](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/e/b/ebc41104f2497aec4fe67efc2ac54f757dad32be.png) ---
**Author:** ![hotwheels](https://avatars.discourse-cdn.com/v4/letter/h/3ab097/32.png) [@hotwheels](https://community.weweb.io/u/hotwheels)\ **Post date:** [May 12, 2026, 4:55pm UTC](https://community.weweb.io/t/new-xano-integration-weweb-unify-is-not-working-well/21194/3 "2026-05-12T16:55:00Z")
**Image #3** ![Weweb-Screenshot 2026-05-02 at 4.37.35 PM (1)](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/3X/a/8/a81efdc0f56085bf8740671ef9038f062d1219af.jpeg) ---
**Author:** ![Perales](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/perales/32/15913_2.png) [@Perales](https://community.weweb.io/u/Perales)\ **Post date:** [May 12, 2026, 8:49pm UTC](https://community.weweb.io/t/new-xano-integration-weweb-unify-is-not-working-well/21194/4 "2026-05-12T20:49:03Z")
Thanks for documenting this. I was considering moving from the Xano plugin to the new Xano integration, but based on your experience I’ll probably wait until the integration becomes more stable. For those of us building real apps and getting close to launch, predictable behavior matters a lot. Even small issues around binding variables, API inputs, authentication, or scoped data can create serious friction. I really like WeWeb and want to keep building with it, but I do hope the team focuses on the no code product instead of vibe coding trends. A more stable and reliable integration would make a big difference for confidence before launch. ---
**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\ **Post date:** [May 13, 2026, 8:42am UTC](https://community.weweb.io/t/new-xano-integration-weweb-unify-is-not-working-well/21194/5 "2026-05-13T08:42:50Z")
Hey @hotwheels 👋 Thanks so much for taking the time to put this feedback together, it’s super thoughtful and helpful to us! Just shared with the product team so they can take a look. ---
**Author:** ![SynopsisLabs](https://avatars.discourse-cdn.com/v4/letter/s/9dc877/32.png) [@SynopsisLabs](https://community.weweb.io/u/SynopsisLabs)\ **Post date:** [May 13, 2026, 3:52pm UTC](https://community.weweb.io/t/new-xano-integration-weweb-unify-is-not-working-well/21194/6 "2026-05-13T15:52:54Z")
Hi, I have had issues with the integration as well [as shown here](https://community.weweb.io/t/dont-fully-understand-new-table-and-views/21161/8) and decided to stick with the plugin until the integration gets more stable. Steve ---
**Author:** ![EvilHIdden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/evilhidden/32/7014_2.png) [@EvilHIdden](https://community.weweb.io/u/EvilHIdden)\ **Post date:** [June 13, 2026, 1:30pm UTC](https://community.weweb.io/t/new-xano-integration-weweb-unify-is-not-working-well/21194/7 "2026-06-13T13:30:51Z")
**Here’s the workaround** You need to recreate the full object payload. It’s a pain and is clearly a WeWeb UI/UX issue, but the underlying logic still work on the API call itself. You can use the native WeWeb `createObject()` formula to recreate the payload. As an example using the original screenshot, `createObject('org_id',`_`value`_`,'search_value', `_`value`_`)` This should still be fixed by WeWeb on their front-end.