Bubble with Xano

Need help
1

Hi everybody,

I’m wiring Bubble to a Xano backend. I keep my APIs split in Bubble:

  • Public API (Auth = None or self-handled) for /auth/signup and /auth/login

  • Private API (same auth, shared header Authorization: Bearer <token>)

I’m trying to initialize the signup call.

Bubble call

  • Method: POST

  • URL: https://<my-xano-base-url>/auth/signup

  • Header: Content-Type: application/json

  • Body (JSON):

{
  "name": "<name>",
  "email": "<email>",
  "password": "<password>",
  "confirm_password": "<confirm_password>"
}

For init I fill test values (not private) so they become dynamic later.

Xano endpoint (Function Stack)

  1. Precondition: inputs present (email, password, confirm_password) → 400 if missing

  2. Precondition: password == confirm_password → 400 if not

  3. Get Record from users by email → existing_user

  4. Precondition: existing_user == null → 409 if email already exists

  5. Hash password → hashedPassword

  6. Add Record in users (password = hashedPassword) → users1

  7. Create Authentication Token → authToken

  8. Response: { token: authToken, user: users1 } (password not exposed)

What happens

  • In Xano “Run”, the endpoint works (creates user and returns token).

  • In Bubble API Connector (Initialize call) I’ve seen an error:

Status code 500
{"code":"ERROR_FATAL","message":"Invalid name: mvpw121831:570491"}
  • The “Invalid name …” seems to happen only when the request comes from outside Xano (Bubble/Postman).

Questions for the community : Has anyone seen 500 “Invalid name …” from a Xano token step when calling from Bubble? Was it due to cookie/header naming? I don’t know how to manage this…

1 Like
2

I see what you’re trying to achieve thanks for laying out the details so clearly. The flow looks correct overall, but the error you’re hitting (Invalid name: mvpw121831:570491) usually points to an issue with headers or environment-specific naming inside Xano. A couple of things to check:

Header formatting in Bubble

In the API Connector, make sure your header is exactly:

Content-Type: application/jsonand that there aren’t extra spaces or mismatched capitalization.

Body field names

Double-check that the JSON fields(name, email, password, confirm_password) match exactly with what your Xano endpoint expects. Even a minor mismatch can cause a 500.

Authentication Token Step

The error message you’re seeing can happen if the auth token step in Xano tries to pull a user field or environment variable with an invalid name. Try temporarily disabling the “Create Authentication Token” step in your function stack and test again if the request goes through, the issue is in how that step references the user object.

Outside requests vs. Xano “Run”

Since it works inside Xano but not outside, I’d also check whether the endpoint requires any implicitheaders (like x-api-key) that aren’t being passed from Bubble. If you’re using environments in Xano, confirm that the external base URL matches your environment’s config.

If you’d like, I’d be happy to take a quick look at your API setup inside Bubble and Xano (via Collab/temporary access) and help you troubleshoot directly. Sometimes these small mismatches are easier to spot hands-on.

Best,

Hans

3

Hello @hankskiprop15,

First of all, sorry for the delay in replying.

A big thank you for your explanations — thanks to what you said about the implicit headers, I looked into it and indeed, there was an issue in my configuration!

Thank you so much.

1 Like
4

No worries at all, I’m really glad to hear that helped you figure it out . Happy I could point you in the right direction. Keep going

5

This topic was automatically closed after 70 days. New replies are no longer allowed.