Xano integration

Xano is a backend platform for databases, APIs, sign in, realtime updates, and streaming responses. The Xano integration lets you connect a Xano workspace to WeWeb so you can use Xano endpoints as table data sources and call Xano from workflows.

What this integration supports

Once connected, you can:

• Use Xano GET endpoints as data sources for WeWeb tables.
• Call Xano endpoints from workflows with the API Request action.
• Optionally connect branching, alternate data sources, realtime, and global headers.

Setup in Xano

Before connecting Xano to WeWeb, make sure you have:

1. A Xano account.
2. A Xano Meta API Key.
3. Access to the Xano Instance and Workspace you want to connect.
4. At least one API group with working OpenAPI docs if you want WeWeb to list endpoints and inputs correctly.

Optional setup:

• A Custom Domain if you do not want to use the default Xano instance domain.
• An X-Data-Source header if you use multiple Xano data sources.
• An X-Branch header if you use Xano branching.
• A Connection Hash if you want to use Xano Realtime.

Get your Meta API Key

Create your Meta API Key in Xano account settings. WeWeb uses this key to list your Xano instances, workspaces, and API groups while you set up the connection.

Check your API group docs

WeWeb reads your Xano API groups through the OpenAPI docs that Xano generates.

If your API groups or endpoint inputs do not appear correctly in WeWeb, test the OpenAPI docs in Xano first. If the docs are broken there, WeWeb cannot read the endpoint structure.

Connect Xano in WeWeb

1. Go to the Integrations tab.
2. Open Integrations.
3. Select Xano.
4. Click Add Integration.
5. Click Add connection.
6. Fill in these required fields:
   • Meta API Key
   • Instance
   • Workspace
7. Add optional fields if your Xano setup needs them:
   • Custom Domain
   • X-Data-Source
   • X-Branch
   • Connection Hash
   • Global Headers

WeWeb stores these settings per environment, so you can use one Xano setup in the editor and another in production if needed.

Use Xano as a table data source

You can use a Xano GET endpoint as the source for a WeWeb table.

1. Go to Data & API → Tables.
2. Click + Add table.
3. Choose Xano as the data source.
4. Select the Xano connection you want to use.
5. Choose the API Group.
6. Choose the Endpoint (GET).
7. Set any default URL Params, Query Parameters, or Headers.

You can then add dynamic parameters at the view level inside the table.

Important pagination note

Xano manages its own pagination for Xano-backed tables.

That means generic WeWeb pagination patterns such as Change page, Load more, and the Paginator element are not compatible with Xano tables. Instead, configure the paging inputs your Xano endpoint expects.

Use Xano in workflows

Once the integration is connected, you can use the API Request action in workflows.

This is useful when you want to:

• Create or update records in Xano.
• Trigger custom business logic in Xano.
• Call protected endpoints using the current signed-in Xano session.
• Stream partial responses for chat or long-running flows.

Streaming responses

Stream Response is available only in Interface workflows, not in backend API Endpoint workflows.

Your Xano endpoint must already be set up to stream. WeWeb can display the streamed response, but it cannot turn a normal Xano response into a streaming one.

Use Xano for sign in

If you want Xano to power sign in for your app, set Xano as your Authentication System in Data & API → Authentication.

When Xano is your Authentication System, WeWeb gives you:

• An On user load trigger to refresh the session.
• Auth workflow templates for Sign In, Sign Up, and Log Out.
• Xano auth actions such as Authenticate, Set User, and Clear Session.

For the full setup flow, see Xano (Authentication System) →.

Common pitfalls

The API group or endpoint does not appear in WeWeb

This is usually caused by broken or incomplete OpenAPI docs in Xano. Check the API group in Xano first and make sure the docs load correctly there.

The wrong environment is connected

If something works in the editor but fails in production, make sure the right Xano Instance, Workspace, Custom Domain, branch, and data source are set for each environment.

Xano table pagination behaves strangely

Xano-backed tables expect Xano's own paging inputs. If you try to use generic WeWeb pagination controls, the results may not match what you expect.

Branch or data source changes are not applied

If you use branching or multiple data sources, make sure Branching is enabled in the Xano connection before filling X-Data-Source and X-Branch.

Realtime does not connect

If you enable Realtime, make sure the Connection Hash matches your Xano Realtime setup.

Auth succeeds but the user still looks signed out

Saving a token is only one part of the flow. In Xano auth setups, make sure your workflow stores the session with Authenticate, then loads the current user and finishes with Set User.

All actions

This integration provides actions you can use in workflows or auth flows.

Authenticate, Set user, and Clear session are available when Xano is the current Authentication System in Data & API → Authentication.

Action	Description
API Request	Call a Xano endpoint from a workflow.
Authenticate	Store the Xano session in WeWeb after sign in or sign up.
Set user	Save the current signed-in user in WeWeb.
Clear session	Log the user out by clearing the Xano session in WeWeb.

Action details

API Request

Call a Xano endpoint from a workflow.

Inputs

Field	Description
API Group	The Xano API group you want to use.
Endpoint	The endpoint path and method.
URL Params	Values for path parts such as {id}.
Query Parameters	Values sent in the URL query string.
Body	Data sent to Xano for POST, PUT, and PATCH requests.
Custom Headers	Extra headers sent with this request.
Stream Response	Streams the response in real time. Only available in Interface workflows for supported methods.

If the current user already has a Xano session, WeWeb sends that session to Xano automatically.

Learn more about the Xano request action →

Authenticate

Store the Xano session in WeWeb after sign in or sign up.

Inputs

Field	Description
Auth Token	The main token returned by your Xano sign-in or sign-up endpoint.
Refresh Token	An optional refresh token, if your Xano flow returns one.
Metadata	Optional extra session data to store with the session.
Persist Session	Keeps the session on the client side so the user stays signed in after refresh.

This action is usually part of the Sign In and Sign Up auth templates.

Authenticate (Xano auth) →

Set User

Save the current signed-in user in WeWeb.

Inputs

Field	Description
User	The user object returned by your Xano current-user endpoint.

This is what makes the current user available for access checks and for display in the interface.

Set user (Xano auth) →

Clear Session

Log the user out by clearing the Xano session in WeWeb.

Inputs

This action has no inputs.

Clear session (Xano auth) →

Reference

Connection settings

Setting	What it means	Where it comes from
Meta API Key	Lets WeWeb list your Xano instances, workspaces, and API groups.	Xano account settings
Instance	The Xano instance you want to connect.	Selected from your Xano account
Workspace	The workspace WeWeb should use.	Selected from the chosen instance
Custom Domain	Optional custom base domain for requests.	Your Xano custom domain setup
X-Data-Source	Optional header for choosing a Xano data source.	Your Xano data source setup
X-Branch	Optional header for choosing a Xano branch.	Your Xano branching setup
Connection Hash	Optional value for Xano Realtime.	Xano Realtime settings
Global Headers	Extra headers added to all Xano requests from this connection.	Your own Xano or app setup

Notes

• Xano tables use GET endpoints only.
• Table views can add dynamic URL Params, Query Parameters, and Headers on top of the table defaults.
• If you use a Custom Domain, WeWeb uses that domain instead of the default Xano instance domain.

FAQs

Can I use Xano as both my data source and my auth system?

Yes. You can connect Xano in Integrations for tables and workflow requests, and also choose Xano in Data & API → Authentication if you want Xano to handle sign in.

Can I use non-GET endpoints as table data sources?

No. Xano-backed tables use GET endpoints. For POST, PUT, PATCH, or DELETE, use the API Request action in a workflow instead.

Why are my endpoint inputs missing?

WeWeb reads the endpoint structure from Xano's OpenAPI docs. If those docs are incomplete or broken in Xano, the inputs may not appear correctly in WeWeb.

Can I stream Xano responses in backend workflows?

No. Stream Response is available in Interface workflows only.

Do I need to send the auth token manually in every Xano request?

Not when you use the Xano integration and the user already has a Xano session in WeWeb. The integration sends the current Xano session automatically.

CONTINUE LEARNING

Next, learn how to configure Xano as your Authentication System and build sign-in, sign-up, and sign-out flows.

Xano authentication system →