Appearance
Authenticate (Xano auth) ​
Use this action after a successful Xano sign-in or sign-up request when you want WeWeb to treat the user as signed in.
Overview ​
Authenticate stores the current Xano session in WeWeb.
This is usually used right after:
- A Xano sign-in request.
- A Xano sign-up request.
- Any custom Xano flow that returns an auth token.
Add the action ​
- In an
Interfaceworkflow, click+ Add action. - Select
Xano→Authenticate.
Configure the action ​
- Auth Token: The auth token returned by Xano.
- Refresh Token: An optional refresh token, if your Xano flow returns one.
- Metadata: Optional extra session details.
- Persist Session: If enabled, keeps the session after refresh.
Most Xano templates map authToken and accessToken for you automatically. If your endpoint uses a different key name, update the binding.
Common pitfalls ​
The user still looks signed out ​
Saving the session is only part of the setup. You still need an On user load workflow that fetches the current user from Xano and finishes with Set user.
CONTINUE LEARNING
Next, store the current user in WeWeb after you fetch it from Xano.

