---
title: "QuintaDB integration for LuumenAI"
url: "https://www.luumen.ai/integrations/quintadb/"
entity: SoftwareIntegration
category: "Databases & data platforms"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# QuintaDB integration for LuumenAI

Read QuintaDB forms and records freely, change records as approved steps

## What LuumenAI can do with QuintaDB

LuumenAI connects to QuintaDB with an API token and exposes 12 tools (7 read-only · 4 write · 1 destructive). For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

## Key facts

- Authentication: API token
- Tools available: 12 tools (7 read-only · 4 write · 1 destructive)
- Deployment: scoped as part of your Pilot, Platform, or Managed rollout
- Category: Databases & data platforms

## About QuintaDB with LuumenAI

Connect QuintaDB with an API key and your team can ask about the data it already keeps there. Luumen lists forms, reads field definitions, pulls records, and searches with explicit predicates. When a record needs to be created, updated, or removed, the agent shows the field IDs and values first and waits for your approval.

## Example tools

Read-only (7 in total):

- `QUINTADB_GET_DATABASE` — Get metadata and resource counts for one allowed QuintaDB database by app ID.
- `QUINTADB_GET_RECORD` — Get one record by exact ID from an allowed QuintaDB database.
- `QUINTADB_LIST_FIELDS` — List the fields in a QuintaDB form, including field IDs and types.
- `QUINTADB_LIST_FORMS` — List forms/tables in an allowed QuintaDB database, including IDs and record counts needed for field and record operations.
- `QUINTADB_LIST_RECORDS` — Return one page of records from a QuintaDB form, optionally constrained to a report.
- `QUINTADB_LIST_REPORTS` — List QuintaDB reports/views for a form.
- `QUINTADB_SEARCH_RECORDS` — Search records in one QuintaDB form using explicit field or system-column predicates.

Write and destructive (5 in total, subject to configured approval policy):

- `QUINTADB_CREATE_RECORD` — Create one record in a QuintaDB form using values keyed by field ID.
- `QUINTADB_CREATE_RECORDS` — Create 2-100 QuintaDB records using sequential individual API calls in input order.
- `QUINTADB_DELETE_RECORDS_BY_ID` — Permanently delete only the explicitly supplied QuintaDB record IDs from one form.
- `QUINTADB_UPDATE_RECORD` — Update selected fields on one QuintaDB record using a field-ID keyed values object.
- `QUINTADB_UPDATE_RECORDS_BY_ID` — Update 2-100 exact QuintaDB record IDs using sequential individual API calls in input order.

## Frequently asked questions

### How does LuumenAI connect to QuintaDB?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in QuintaDB on its own?

For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

### Is there an audit trail?

Every call to QuintaDB — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/quintadb/