> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xano.com/llms.txt
> Use this file to discover all available pages before exploring further.

# No-Code App Builders

> Connect your Xano backend to no-code platforms like WeWeb, Bubble, and others using native integrations or REST APIs.

No-code app builders can connect to Xano through **native integrations** (plugins built specifically for Xano) or through **standard REST API calls** using your Swagger/OpenAPI documentation. The approach depends on your platform.

***

## WeWeb

WeWeb has dedicated Xano plugins for both data fetching and authentication, making it the most tightly integrated no-code option.

### Data Source Plugin

<Steps>
  <Step title="In WeWeb, navigate to Plugins → Data Sources → Xano" />

  <Step title="Add your Xano connection">
    Supply your **Personal Access Token** (PAT) from the [Metadata API](/xano-features/metadata-api). This allows WeWeb to discover your API groups and endpoints automatically.
  </Step>

  <Step title="Create Collections to fetch data">
    Configure collections for each data set you need. You can set global headers at the plugin or collection level.
  </Step>

  <Step title="If you use the Auth plugin, tokens are forwarded automatically">
    No additional configuration is needed to pass auth tokens with your data requests.
  </Step>
</Steps>

[WeWeb Xano Data Source Documentation](https://docs.weweb.io/plugins/data-sources/xano-data.html)

### Auth Plugin

The WeWeb Xano Auth Plugin handles signup, login, logout, gated content, and role-based redirects.

[WeWeb Xano Auth Plugin Documentation](https://docs.weweb.io/plugins/auth-systems/xano-auth.html)

***

## Bubble

Bubble can connect to Xano in two ways: through a community-built Xano connector, or through Bubble's native API Connector.

### Xano Connector Plugin

A community-driven plugin built around the official Xano JS SDK. It simplifies authentication and supports real-time features.

[Bubble Xano Connector Guide](https://elibeachy.gitbook.io/xano-connector/)

### Bubble API Connector

Use Bubble's built-in API Connector to configure Xano endpoints manually. You'll copy endpoint URLs, methods, headers, and request/response structures from your Swagger documentation.

<Steps>
  <Step title="Get your Swagger documentation URL">
    We recommend using the **combined (workspace-level) Swagger documentation** so you have all endpoints in one place. See [Swagger/OpenAPI Docs](/the-function-stack/building-with-visual-development/apis/swagger-openapi-documentation) for how to enable it.
  </Step>

  <Step title="In Bubble, open the API Connector plugin">
    Go to **Plugins → API Connector** and add a new API.
  </Step>

  <Step title="Configure each endpoint">
    Using your Swagger docs as reference, set the URL, method, headers (`Authorization: Bearer <token>`), and request body for each endpoint you need.
  </Step>

  <Step title="Initialize the call">
    Bubble requires you to initialize each API call to detect the response structure. Make sure your Xano backend has test data available.
  </Step>
</Steps>

[Bubble + Xano API Connector Guide](https://www.xano.com/learn/Connect-Xano-Bubble/)

***

## Other No-Code Platforms (REST API)

Any no-code platform that supports making HTTP/REST requests can connect to Xano. The general approach is the same regardless of the platform:

### General Steps

<Steps>
  <Step title="Get your API endpoint URLs">
    Open your [Swagger/OpenAPI documentation](/the-function-stack/building-with-visual-development/apis/swagger-openapi-documentation) in Xano. We recommend enabling **combined (workspace-level) documentation** so you have all endpoints in one place. Copy the base URL and endpoint paths you need.
  </Step>

  <Step title="Configure your HTTP requests">
    In your no-code platform's API/HTTP request feature, set up:

    * **URL**: Your Xano endpoint URL (e.g., `https://your-instance.xano.io/api:your-group/endpoint`)
    * **Method**: GET, POST, PATCH, DELETE, etc. (as documented in Swagger)
    * **Headers**: `Content-Type: application/json` and `Authorization: Bearer <token>` for protected endpoints
    * **Body**: JSON request body for POST/PATCH requests, matching the schema in your Swagger docs
  </Step>

  <Step title="Handle authentication">
    Call your `auth/login` or `auth/signup` endpoint to get a JWT token. Store the token and include it in the `Authorization` header for subsequent requests.
  </Step>

  <Step title="Map the response data">
    Use your platform's data binding features to map the JSON response from Xano to your UI components.
  </Step>
</Steps>

### Common Platforms

This approach works with platforms like:

* **FlutterFlow** — Use the API Call feature to configure REST endpoints
* **Adalo** — Use Custom Actions or the API Connector to call Xano endpoints
* **Softr** — Connect via the REST API integration
* **Glide** — Use the API integration feature with your Xano endpoints
* **AppGyver / SAP Build Apps** — Configure REST API data sources

<Tip>
  If your no-code platform supports importing an **OpenAPI/Swagger spec**, you can import your combined Swagger JSON directly instead of configuring each endpoint manually. Check your platform's documentation for OpenAPI import support.
</Tip>

***

## Tips

* **Personal Access Tokens** — Platforms with native Xano integrations (like WeWeb) use PATs from the [Metadata API](/xano-features/metadata-api) to discover your API groups. This is separate from the JWT tokens your app's users will use.
* **CORS** — Xano handles CORS automatically. If you encounter issues, check your API group's CORS settings.
* **Branching** — Use [Xano branches](/team-collaboration/branching-and-merging) for backend changes so your production frontend stays stable while you develop.
* **Platform docs first** — For platform-specific configuration (plugin settings, data binding, deployment), the best source of truth is always the platform's own documentation.