Supabase
Supabase client for database CRUD and file storage. Provides full PostgREST operations — select (with filtering, ordering, pagination, single-row mode), insert, update, delete, and upsert (with conflict resolution) — plus storage operations for uploading (from local file or base64), downloading to disk, listing with prefix/pagination, and deleting files. Also supports calling PostgreSQL functions via RPC. All database and storage nodes can work standalone with inline credentials or share a connection via the Connect/Disconnect client ID pattern. Auth uses a single API key credential (anon or service_role).
| Namespace | Robomotion.Supabase |
| Version | 1.1.0 |
| Category | Database, Dev Tools |
| Nodes | 13 |
Nodes
| Node | Description |
|---|---|
| Connect | Opens a connection to Supabase and returns a Client ID. |
| Disconnect | Closes a Supabase connection. |
| Insert Row | Inserts a row in Supabase. |
| Select Rows | Select Rows — see the properties below. |
| Update Rows | Updates rows in Supabase. |
| Delete Rows | Deletes rows in Supabase. |
| Upsert Row | Upsert Row — see the properties below. |
| Upload File | Uploads a file in Supabase. |
| Download File | Downloads a file in Supabase. |
| List Files | Lists files in Supabase. |
| Delete File | Deletes a file in Supabase. |
| Call Function | Call Function — see the properties below. |
| Toolkit | Exposes this package's operations to an AI Agent as a single tool. |
Connecting
This package has a Connect node. Run it once at the start of your flow; it returns a Client ID that the other nodes take as input. Pair it with Disconnect so the connection is released when the flow ends.
Credentials belong in a Vault rather than typed into the node.
AI Agent tools
12 of these nodes are exposed as tools an AI Agent can call directly:
Connect, Disconnect, Insert Row, Select Rows, Update Rows, Delete Rows, Upsert Row, Upload File, Download File, List Files, Delete File, Call Function.
Generated from the package spec that the Flow Designer itself loads, so the node list and every property below match the version above exactly.
It does not yet include worked examples or service-specific guidance — those are written by hand, and a plausible-sounding guess in a reference page is worse than an honest gap. If you build something useful with this package, the community is the place to share it.