Connect external services and understand what belongs outside Adalo.
3 resourcesBegin with the smallest record set that can demonstrate the intended result. Confirm the collection and property types, remove optional filters or conditions, and display one plain value from the current record. Once that basic path works, restore one rule at a time. The first rule that changes the expected result identifies the layer worth investigating.
Keep query logic, component visibility, and actions separate while debugging. A query decides which records are available. Visibility decides whether one interface element appears. An action changes data or navigation state. Treating those as different responsibilities makes it easier to explain both the successful path and the empty, denied, or missing-data states.
The resources below label their evidence and limitations individually. Use the reviewed date to judge freshness, follow current official sources for product behavior, and treat dated forum reports as examples of builder experience rather than guarantees. Finish with the testing checklist on the relevant page, including at least one record that should pass and one that should fail.
Ask about this topic 💬Save the external movie's numeric ID on each internal review, then filter the review list by the current movie's ID.
Documented from current sourcesPut a stable unique property first in an Adalo External Collection response, then retest the connection and confirm every list row maps to a different record.
Community workaroundMove list limits, pagination, and sorting into the Xano endpoint when Adalo does not show its standard Max Items or Sort controls.
Documented from current sources