A Xano node would be game changer

Feature Requests
1

The idea is:

A Xano a note would be a real game changer. Xano is offering all data (tables, and fields) by supportin the OpenAPI spec.

My use case:

Using Xano as a backend in other applications and communicate with workflows in n8n would be create a very good technical solution. By this node all APIs would be available to n8n for updating a table, searching, etc.

I think it would be beneficial to add this because:

By now every communication to Xano has to be created manually via setting up an HTTPrequest GET POST UPDATE … in n8n. For this the n8n user has to verify the API and the body of a POST JSON body request or parameters of a GET by looking at the Swagger documentation. A UI for this would be so smart!!!

Any resources to support this?

Are you willing to work on this?

I’d like to help, but I can’t technically. I understand everything about this features but I’m not able to code. Of course I would help out with strategical planning or project management. But I think a good coder would be able to create this node in no time.

Anyone tried using Xano embeddings with n8n Ai Agents?
2

+1 this suggestion.
Not only does Xano offer the same functionality as Supabase as a database, but Xano also allows the creation of database triggers that would simplify the process of creating vectors (for ai agents) that can be used within n8n.

I think Xano can be used as a database node and also a vector store retrieval node.

إعجاب واحد (1)
3

This would be huge!!! Love n8n!

4

Huge +1 for a Xano node!

5

+1 for a xano node!

6

+1 for a xano node!

7

+1 for a xano node!

8

YES!!! We would abosolutely LOVE to have a Xano Node!!!

9

+1 for Xano node!

10

Great suggestion, a dedicated Xano node would definitely save a ton of time and make n8n workflows much more intuitive. Manually mapping every endpoint via HTTP requests gets tedious fast, especially when you’re dealing with complex JSON bodies or query params.

Since you mentioned the Swagger/OpenAPI spec, that’s actually the perfect hook. If you want to see a clean example of how API docs can be turned into an interactive, user-friendly interface, check out the spike :volleyball:, it’s a platform that does a really nice job of surfacing backend capabilities in a visual way. Not a direct Xano solution, but it shows what’s possible when you abstract away the raw HTTP layer.

Hope that gives you some inspiration. And if any dev here picks this up, I’d be happy to help with testing or use-case validation.