Xano
Backend PlatformWire AI agents into your Xano backend. Agents query, create, update, and delete records through your API groups and call any custom endpoint you have built, with full control over method, path, and payload.
What This Integration Enables
Xano is where no-code teams put their real backend: production tables, authentication, and custom business logic behind user-defined REST endpoints. That last part matters, because a Xano workspace is not a generic database, it is an API you designed. This connector respects that design. FlowRunner agents use the auto-generated CRUD endpoints for standard table operations and Call Endpoint for everything you built yourself, with full control over method, path, query parameters, and body. - Query, create, update, and delete records through Xano's auto-generated table endpoints - Call any custom endpoint in the API group, so your business logic runs, not a bypass of it - Sync records between Xano and CRMs, stores, spreadsheets, and warehouses - Enrich workflow decisions with live reads from production tables - Authenticate with an optional Bearer token where endpoints require it This is a production backend, which means writes reach the data your product runs on. FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) discipline draws the line at the operations that destroy records.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Orders mirrored into the backend that runs the product
Every [Shopify](/integrations/shopify) order triggers Create Record into the orders table, then Call Endpoint against the custom endpoint that allocates inventory and updates the customer's account state, the same logic the app itself would run. The storefront and the product backend stop drifting, and the app's users see their orders without a nightly import.
The backend as the enrichment source
When a support ticket or sales inquiry arrives, the agent calls Query Records and Get Record against the production tables to pull the customer's real state: plan, usage, recent activity. That context lands in the ticket or the CRM record before a human opens it. The backend most teams can only see through the app becomes the source of truth every workflow reads from.
Two-way sync with the operational spreadsheet
Operations still lives partly in [Google Sheets](/integrations/google-sheets), so the agent runs both directions: Query Records exports table changes to the sheet on a schedule, and edited sheet rows come back through Update Record, matched by record ID, with only changed fields sent. Conflicting edits, where both sides changed since the last sync, do not get guessed at; they queue for a person, and a [Slack](/integrations/slack) note says why.
Human-in-Loop Highlight
Delete Record fires a DELETE against a production table and the record is gone, not from a staging copy or an analytics mirror, but from the backend your application is serving to users at that moment. There is no trash folder in an auto-generated endpoint. So destructive sweeps in this connector are proposals by construction: a cleanup agent identifies candidates with Query Records, pulls each full record with Get Record so the reviewer sees exactly what would vanish, and posts the batch for sign-off before a single DELETE is sent. The same caution extends to Call Endpoint when it targets custom routes with irreversible effects, a payment capture, a cascade delete you wrote yourself, because the connector cannot know what your endpoint does, but the person who built it can, and that person approves the call pattern once, deliberately, before it runs unattended.
Agent Capabilities
6 actionsRecords
5- Query Records Lists records from a table via its auto-generated GET collection endpoint, with pagination and whatever filter parameters the endpoint accepts. The read behind syncs, sweeps, and enrichment.
- Get Record Retrieves a single record by ID, returning the full object. The context-gathering step before updates, decisions, and reviewed deletions.
- Create Record Creates a record via the table's auto-generated POST endpoint, with fields matching the table's input schema. Returns the new record with its assigned ID and timestamps.
- Update Record Updates a record by ID via PATCH, sending only the fields that change. The safe default for syncs and status transitions.
- Delete Record Deletes a record by ID via the auto-generated DELETE endpoint, permanently. The operation this page's human gate exists for.
Custom Endpoints
1- Call Endpoint Calls any endpoint in the API group with full control over HTTP method, path, query parameters, and request body, with the configured Bearer token attached when present. The escape hatch that makes your user-defined endpoints, and the business logic inside them, available to every flow.
Frequently Asked Questions
What can FlowRunner do with Xano?
FlowRunner agents can run Call Endpoint, Query Records, and Get Record in Xano, plus 3 more actions.
Does connecting Xano to FlowRunner require OAuth?
No. Xano connects to FlowRunner with an API key, no OAuth flow required.
Can Xano trigger a FlowRunner workflow automatically?
Xano doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Xano
$100 in credits. No card required. Connect in minutes.