Sanaf AI
Start free
Databases

QuintaDB, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your QuintaDB account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Databases
  • Connects with a key
  • 12 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What QuintaDB is

QuintaDB is a no-code online database and application builder for managing databases, forms, fields, records, reports, and files.

You paste in a key from your own QuintaDB account. It is kept encrypted, and you can withdraw it from inside QuintaDB whenever you like.

How a run works

One message in, the work done in QuintaDB.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in QuintaDB. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own QuintaDB account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

12 tools it already has

What it can do in QuintaDB

These are the ready-made tools your AI employee already has in QuintaDB. It is not limited to them, but it never has to be taught these.

  • Create RecordCreate one record in a QuintaDB form using values keyed by field ID. The tool supplies QuintaDB's required entityid inside the nested values body.
  • Create RecordsCreate 2-100 QuintaDB records using sequential individual API calls in input order. This is not atomic: some records can succeed while others fail, and every item returns its own o
  • Delete Records By IDPermanently delete only the explicitly supplied QuintaDB record IDs from one form. This tool never supports delete-all or filter-based deletion.
  • Get DatabaseGet metadata and resource counts for one allowed QuintaDB database by app ID. Use this instead of global database discovery when the API key is restricted to selected apps.
  • Get RecordGet one record by exact ID from an allowed QuintaDB database. Values are returned under their field IDs for reliable use with QuintaDB schema and record tools.
  • List FieldsList the fields in a QuintaDB form, including field IDs and types. Use these IDs as keys in record values and search predicates.
  • List FormsList forms/tables in an allowed QuintaDB database, including IDs and record counts needed for field and record operations.
  • List RecordsReturn one page of records from a QuintaDB form, optionally constrained to a report. Record values remain keyed by field ID for reliable use with schema and write tools.
  • List ReportsList QuintaDB reports/views for a form. Use a returned report ID to constrain record listing or search.
  • Search RecordsSearch records in one QuintaDB form using explicit field or system-column predicates. Groups are combined with OR; predicates inside each group are combined with AND.
  • Update RecordUpdate selected fields on one QuintaDB record using a field-ID keyed values object.
  • Update Records By IDUpdate 2-100 exact QuintaDB record IDs using sequential individual API calls in input order. This is not atomic: some updates can succeed while others fail, and every item returns
Access, and who is in charge of it

You stay the boss of your QuintaDB account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own QuintaDB account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in QuintaDB is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in QuintaDB and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about QuintaDB

Can an AI employee really work inside QuintaDB?
Yes. It signs in to your own QuintaDB account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of QuintaDB?
No. Nothing moves and nothing is replaced. Your records stay in QuintaDB, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my QuintaDB account?
You paste in a key from your own QuintaDB account. It is kept encrypted, and you can withdraw it from inside QuintaDB whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in QuintaDB?
It has 12 ready-made tools in QuintaDB today, among them Create Record, Create Records and Delete Records By ID. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use QuintaDB and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in QuintaDB and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in QuintaDB?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in QuintaDB is written down with what it did and when.