Database
The Database section is the workspace’s JSON document store. Documents live in
collections; workflows read and write them through the db_* nodes, and this screen is
where you look at that data with your own eyes and fix it by hand.
Database / users
users
128 documents · 412 KB · 3.1 MB / 1 GB used
| _id | Document |
|---|---|
| 9f13c0a2… | { "name": "Ada", "age": 36, "tags": ["vip"] } |
| b7e4d115… | { "name": "Boris", "age": 17 } |
Collections
- Open Database. A “Collections” submenu appears in the sidebar.
- Press “+” next to the submenu title — or the “New collection” button on the empty screen.
- Give it a name (required) and, optionally, a description. The name is unique inside the workspace: a repeat returns an error.
Clicking an entry in the submenu opens the collection. Under its name you get the document count, the bytes it occupies and the workspace’s quota reading.
The trash icon next to the name deletes the collection with all of its documents; the action is confirmed by a dialog and cannot be undone. The freed bytes return to the quota counter immediately.
Documents
The list shows the first 50 documents of the collection, sorted by _id. Each card is an
identifier plus the document’s full JSON.
- Insert opens a JSON editor. The body must be an object: an array, a string or a number is rejected with “Document must be a JSON object”.
- You may set
_idyourself. Without it, the platform generates a UUID. - Edit opens the same editor with the current content. Saving replaces the document
as a whole:
_idis preserved, every other field comes from the JSON you typed. - The trash icon on a document row deletes it right away, with no confirmation.
Queries
The field above the list takes a MongoDB-style filter. It starts as {} — “every
document”. The “Query” button runs the filter and shows up to 100 matches.
Supported operators:
| Group | Operators |
|---|---|
| Comparison | $eq, $ne, $gt, $gte, $lt, $lte |
| Inclusion | $in, $nin |
| Logic | $and, $or, $not, $nor |
| Element | $exists |
| Arrays | $size |
| Strings | $regex |
A path into a nested field uses dots: user.name, tags.0. An unknown operator is a
query error, not an empty result.
Quotas and limits
The “used” line compares this workspace’s bytes against the effective limit. There are in fact two ceilings, and they bound different quantities:
- the workspace ceiling — how far this workspace’s counter may grow;
- the owner’s plan ceiling — the total across every workspace they own.
The screen shows whichever of the two has less headroom left, so the reading never
disagrees with the limit a write actually hits. 0 on either side means “unlimited”.
Beyond total size there are two per-item limits, set at deployment: the size of a single document (1 MB by default) and the number of documents in a collection (1,000,000 by default). A write past either is rejected with 413 rather than truncated.
The number of collections is capped by the plan (max_collections) — once it is spent,
creating another collection returns a quota error.
Permissions
Any workspace member can read collections and documents. Creating a collection and inserting, editing or deleting documents requires the editor or admin role; a viewer gets a 403 from the server.