n8n and backend services: Part 5 — Xano

Xano — a cloud platform for building backends without coding. Database tables and API logic are assembled in a visual editor: input parameters, database queries, conditions, loops, calls to external services. Each such workflow is published as a REST endpoint that the frontend, mobile app, or n8n calls.

What Xano consists of

• Database — tables with a visual schema editor; PostgreSQL underlies it.
• API builder — a chain of functions (function stack) for each endpoint: fetch data, filter, transform, write, call external API.
• Authentication — users, tokens, permission checks on endpoints.
• Database triggers — logic that runs when a record is added, changed, deleted, or when a table is cleared.
• Background tasks — scheduled workflows.

The main difference between Xano and Supabase or Appwrite is that business logic lives inside the platform, not in the application code. This is convenient for teams without backend developers, but moving such logic to another platform must be done manually.

Pricing

According to Xano’s website as of September 2026 (prices when billed annually):

The Free plan is suitable only for development due to the rate limit. Self-hosting exists but only on the Custom plan.

Xano and Russian projects

Xano’s cloud plans operate abroad, and they cannot be paid with a card from a Russian bank. For initial collection of personal data of Russian citizens, cloud Xano is not suitable: since July 1, 2025 such data must be collected in databases located in Russia. The Custom plan with hosting on your own servers formally solves the issue, but its terms and the possibility of concluding a contract with a Russian company must be clarified directly — there is no public information about this.

For a Russian project with user data, Supabase or Appwrite on your own server is more practical. Xano remains an option for foreign projects and for data without personal information.

How to connect Xano to n8n

Xano node. There is a node n8n-nodes-xano for n8n. It is developed by Xano itself, and n8n has reviewed and included it in the list of verified community nodes; it can be installed in cloud n8n and on a self-hosted server. The owner of the n8n instance installs the node, after which others can use it. Node operations:

• create a row and create multiple rows in a single request;
• get a row, get multiple rows, find rows by condition;
• update a row by identifier and update multiple rows at once;
• delete a row.

To connect you need the Metadata API token from Xano settings.

HTTP Request to your endpoints. The node works with tables directly. If business logic — validations, calculations, related records — is already assembled in Xano, it’s more reliable to call its endpoint with the HTTP Request node so that n8n does not bypass those rules. Authorization — token in the Authorization: Bearer … header if the endpoint is protected.

How Xano notifies n8n about changes

A table trigger in Xano fires when a record is added, changed, or deleted. In the trigger function chain, add an External API Request step with the n8n Webhook address and pass the changed record in the body.

The opposite direction — n8n sending data to Xano — is arranged the same: in Xano you create a POST endpoint that accepts the request. Xano documentation recommends verifying the signature of incoming requests (filters like hmac_sha256 and others) or a static token in a header.

Process examples

Notification about a large order. Table trigger on orders for record creation → External API Request to n8n → IF: amount greater than threshold → message to the head of sales.

Bulk import. Schedule Trigger → export from an external API → Loop Over Items node splits data into batches → Xano node creates rows in batches. Batch loading saves requests and avoids hitting the rate limit.

Asynchronous processing for a mobile app. The app calls a Xano endpoint, which saves the request and immediately replies to the client, while long-running work — document generation, calls to third-party services — is handed off to n8n via External API Request. When n8n finishes, it updates the record in Xano.

When to choose Xano

• A foreign project, the team has no backend developer, and API logic needs to be changed quickly.
• Logic is more important than direct database access: it’s convenient to assemble and validate it in a visual editor.
• Budget allows a paid plan: the Free plan is only enough for development.

Typical mistakes

• Running a workflow on the Free plan. The 10-requests-per-20-seconds limit quickly causes errors for any mass process.
• Writing to tables bypassing business logic. If validations are assembled in an endpoint, a node that writes directly to the table bypasses them.
• An open webhook without verification. An endpoint that accepts data from n8n must verify a token or signature.
• Logic that has nowhere to be migrated. Before choosing a platform, evaluate what will happen if you need to leave it: Xano scenarios must be rewritten manually.