Xano setup

Connecting Xano takes a few minutes: you create a key in Xano, paste it in WeWeb, then pick the instance and workspace you want to use. Once the connection exists, you can use it in tables and in workflows.

Before you start

Before connecting Xano to WeWeb, make sure you have:

1. A Xano account with access to the instance and workspace you want to connect.
2. A Xano Metadata API key. WeWeb uses it to list your instances, workspaces, API groups, and endpoints while you build.
3. Working API documentation (Swagger) for your API groups. WeWeb reads it to know which endpoints exist and which inputs each one expects.

Create a Metadata API key

1. In Xano, open your account settings.
2. Create a Metadata API key.
3. Copy it: you'll paste it in WeWeb in the next step.

Learn more about the Metadata API in the Xano docs →

CHECK YOUR API DOCUMENTATION FIRST

If an API group or the inputs of an endpoint don't appear in WeWeb, open the API documentation of that group in Xano. If it doesn't load there, WeWeb can't read it either. This is often caused by an empty input or variable in one of the endpoints of the group.

Connect Xano in WeWeb

1. Go to the Data & API tab, then open the Integrations subtab.
2. Select Xano.
3. Click Add Integration.
4. Click Add Connection.
5. Paste your key in Meta API Key.
6. Select your Instance. The list shows each instance with its domain.
7. Select your Workspace.
8. (Optional) Fill in Custom Domain, Branching, and Global Headers if your Xano setup needs them. See Optional settings below.

If the Instance or Workspace list looks out of date, click the refresh button next to it.

Use different settings per environment

At the top of the connection, the Environment selector lets you switch between your environments (for example Editor, Staging, and Production). Each environment has its own Meta API Key, Instance, Workspace, Custom Domain, and branching settings.

This is useful when your app should use a test workspace or branch while you build in the editor, and your live workspace once published.

Global Headers are the exception: they are shared by all environments.

Optional settings

Custom domain

By default, WeWeb sends requests to the domain of the instance you selected. If you set up a custom domain in Xano, paste it in Custom Domain to use it instead.

Enter the full address, including https://, for example https://api.my-domain.com. An incomplete address makes requests fail or return unexpected results.

Branching

If you use Xano branches or several Xano data sources, set Branching to Enabled. Two fields appear:

• X-Branch: The name of the Xano branch your app should use.
• X-Data-Source: The name of the Xano data source your app should use.

Leave a field empty to use your Xano default. When Branching is Disabled, WeWeb ignores both fields, and setting it back to Disabled clears them.

Global headers

Global Headers are sent with every request made through this connection, from tables and from workflows. Click Add Property, then fill in a Key and a Value for each header.

To add a header to a single table or request only, use the Headers field of the table or the Custom Headers field of the API Request action instead.

Connection settings

Setting	What it means	Where it comes from
Meta API Key	Lets WeWeb list your Xano instances, workspaces, API groups, and endpoints. Required.	Your Xano account settings
Instance	The Xano instance WeWeb connects to. Required.	Listed from your Xano account
Workspace	The Xano workspace WeWeb uses. Required.	Listed from the selected instance
Custom Domain	A full address, including https://, used instead of the instance domain.	Your Xano custom domain setup
Branching	Turns the X-Branch and X-Data-Source fields on or off.	Your choice
X-Branch	The Xano branch your requests use.	Your Xano branches
X-Data-Source	The Xano data source your requests use.	Your Xano data sources
Global Headers	Headers added to every request of this connection, in all environments.	Your own Xano setup

CONTINUE LEARNING

Your connection is ready. Next, decide which role Xano plays in your app: your whole backend, a data source behind WeWeb, or both.

Choose how to use Xano →