Help Needed: Adalo Team Plan Advanced Table Integration with Xano APIs - Response Format Requirements?

Get Help External Collections, Custom Actions & Collections
1

Hi All,

I’m trying to integrate my Xano users API with Adalo’s Team plan advanced table feature, but I’m running into issues where Adalo does not recognise my users API, even though:

  • My API works perfectly in Postman.
  • It’s accepted and works as an external API integration in Adalo.
  • My API follows standard REST conventions:
    • /users returns a JSON array of user objects with numeric id fields.
    • /users/{id} returns a single JSON object.
  • I’ve removed sensitive fields like passwords.
  • Field names are consistent and use standard casing.
  • There’s working data in the tables
  • There are now Swagger authentication requirements (all public and published)

Xano support confirmed that there are no documented special response format or schema requirements for this feature beyond standard REST patterns.
Adalo’s documentation and forums don’t provide clear guidance on any additional requirements or sample schemas for the Team plan advanced table integration.

Has anyone successfully connected Xano APIs to Adalo’s Team plan advanced tables?
Are there any undocumented response format requirements, metadata, or schema patterns that Adalo expects for this integration?
Any example responses or tips would be hugely appreciated!

I flagged a support ticket, but I received a reply with only a setup document link (I’ve read and watched all the Adalo and Xano information on this).

Any help or insight would be greatly appreciated.

Thanks in advance!

2

@theadaloguy @Victor - any ideas? I even tested this again by creating a new workspace in Xano with the Adalo-linked users table. Added a record, and even with this new base URL, it still says it can’t find the users API (tried naming ‘user’ and ‘users’)