# Custom Endpoint not Showing in Adalo

When you connect Xano to Adalo, only certain types of data can be imported automatically. These are called **collections**, and they come directly from the tables in your Xano database.

### **What Is a Collection?**

In Xano, when you create a table (for example, a table called "Products"), Xano automatically creates a set of basic API endpoints that let you create, read, update, and delete items from that table. These are called **CRUD endpoints** and they are linked to your actual database. Adalo recognizes these as **collections**, which is why they show up when you click "Import Xano Collection."

### **What Is a Custom Endpoint?**

A **custom endpoint** is something you build yourself in Xano, usually in the API section. You might use it to run logic, combine data, or return a filtered list. Even if it returns a list of records, Adalo does **not** consider it a collection, so it will **not** appear in the Import menu.

### Why Custom Xano Endpoints Do Not Show in the Import Collection Menu

When connecting your Xano backend to Adalo, it's important to understand the difference between **collections** and **custom endpoints**, and how each works within Adalo.

#### What Shows Up in "Import Xano Collection"

When you click **Import Xano Collection** in Adalo, only database tables from Xano's **Default API group** will appear. These are the tables where Xano automatically creates built-in API endpoints that allow you to:

* Create items
* Read items
* Update items
* Delete items

These built-in endpoints are called **CRUD endpoints**, and they are tightly linked to your Xano database. Adalo uses them to recognize and sync your data collections.

> ✅ These are what Adalo considers **collections**.

***

#### Why Custom Endpoints Are Not Included

If you created your own **custom endpoint** in Xano — even if it’s a GET request that returns a list — it will **not** appear in the import list. That’s because Adalo only pulls in database-connected collections, not manually created or logic-based endpoints.

> ❌ Custom endpoints are not automatically recognized as collections by Adalo.

This is true even if:

* The endpoint is published
* Authentication is disabled
* It returns a valid list or array

### **How to Use Custom Endpoints in Adalo**

Even though custom endpoints do not show up in the collection list, you can still use them in your app:

* Use an [**External Collection**](/integrations/external-collections-with-apis.md) if your custom endpoint returns a list of items you want to display (like a list of filtered products).
* Use a [**Custom Action**](broken://pages/-M8SNZbnXsFsAqN4uxdY) if your custom endpoint performs an action (like submitting a form or running calculations).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.adalo.com/integrations/xano-integration/troubleshooting-xano/custom-endpoint-not-showing-in-adalo.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.