---
canonical_url: "https://docs.composio.dev/toolkits/quintadb"
markdown_url: "https://docs.composio.dev/toolkits/quintadb.md"
product: "platform"
version: null
last_updated: null
---

# QuintaDB

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

- **Category:** databases
- **Auth:** API_KEY
- **Composio-managed OAuth available?** N/A
- **Tools:** 12
- **Triggers:** 0
- **Slug:** `QUINTADB`
- **Version:** 00000000_00

## Tools

### Create Record

**Slug:** `QUINTADB_CREATE_RECORD`

Create one record in a QuintaDB form using values keyed by field ID. The tool supplies QuintaDB's required entity_id inside the nested values body.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `entity_id` | string | Yes | The destination form/table ID. The tool inserts this as values.entity_id for QuintaDB. |
| `record_id` | string | No | Optional caller-generated 22-character URL-safe record ID. Usually omit this and let QuintaDB generate one. |
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |
| `field_values` | object | Yes | Non-empty object mapping QuintaDB field IDs to values. Obtain field IDs with QUINTADB_LIST_FIELDS; do not use display names as keys. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Records

**Slug:** `QUINTADB_CREATE_RECORDS`

Create 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 outcome.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `records` | array | Yes | Between 2 and 100 records to create sequentially in the supplied order. Each item becomes a separate QuintaDB API request. |
| `entity_id` | string | Yes | The destination QuintaDB form/table ID used for every record. |
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Records By ID

**Slug:** `QUINTADB_DELETE_RECORDS_BY_ID`

Permanently delete only the explicitly supplied QuintaDB record IDs from one form. This tool never supports delete-all or filter-based deletion.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `entity_id` | string | Yes | The form/table ID containing the records. |
| `record_ids` | array | Yes | Non-empty explicit list of exact record IDs to permanently delete. Verify these IDs before calling. |
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Database

**Slug:** `QUINTADB_GET_DATABASE`

Get 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Record

**Slug:** `QUINTADB_GET_RECORD`

Get 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `record_id` | string | Yes | The exact record ID. |
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Fields

**Slug:** `QUINTADB_LIST_FIELDS`

List the fields in a QuintaDB form, including field IDs and types. Use these IDs as keys in record values and search predicates.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `entity_id` | string | Yes | The form/table ID whose fields should be listed. |
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Forms

**Slug:** `QUINTADB_LIST_FORMS`

List forms/tables in an allowed QuintaDB database, including IDs and record counts needed for field and record operations.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Records

**Slug:** `QUINTADB_LIST_RECORDS`

Return 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | One-based page number to return. Start with 1 and use next_page to continue. |
| `per_page` | integer | No | Records requested per page. QuintaDB plan limits vary; reduce this if the provider rejects the value. |
| `entity_id` | string | Yes | The form/table ID whose records should be listed. |
| `report_id` | string | No | Optional report/view ID from QUINTADB_LIST_REPORTS used to constrain the records. |
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Reports

**Slug:** `QUINTADB_LIST_REPORTS`

List QuintaDB reports/views for a form. Use a returned report ID to constrain record listing or search.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `entity_id` | string | Yes | The form/table ID whose reports should be listed. |
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Search Records

**Slug:** `QUINTADB_SEARCH_RECORDS`

Search 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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Maximum records to return, from 1 through 200. |
| `entity_id` | string | Yes | The form/table ID to search. |
| `report_id` | string | No | Optional report/view ID from QUINTADB_LIST_REPORTS used to constrain the search. |
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |
| `search_groups` | array | Yes | Non-empty OR groups. Every group must contain at least one predicate; predicates within one group are combined with AND. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Record

**Slug:** `QUINTADB_UPDATE_RECORD`

Update selected fields on one QuintaDB record using a field-ID keyed values object.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `record_id` | string | Yes | The exact record ID to update. |
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |
| `field_values` | object | Yes | Non-empty object mapping only the QuintaDB field IDs to change to their new values. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Records By ID

**Slug:** `QUINTADB_UPDATE_RECORDS_BY_ID`

Update 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 its own outcome.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `updates` | array | Yes | Between 2 and 100 exact-ID updates to perform sequentially in the supplied order. Each item becomes a separate QuintaDB API request. |
| `database_id` | string | Yes | The QuintaDB database ID from its URL, where it appears after /apps/. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |