# QuintaDB integrations: databases, forms and fields

> Create a database, create a form and create a field in QuintaDB. Connect QuintaDB to the rest of your data and analytics stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/quintadb-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

QuintaDB is an online database builder where you design forms and tables, store records with files and relationships, and share data through reports and portals. Tray.ai connects to QuintaDB through the HTTP Connector, so your workflows can call the QuintaDB API alongside the rest of your stack.

## Use cases

### Databases

Read, create, update, and delete databases in QuintaDB from any Tray.ai workflow. The QuintaDB API covers calls such as list databases and get a database.

- List databases
- Get a database
- Create a database

### Forms

Read, create, update, and delete forms in QuintaDB from any Tray.ai workflow. The QuintaDB API covers calls such as list forms and get a form.

- List forms
- Get a form
- Create a form

### Fields

Read, create, update, and delete fields in QuintaDB from any Tray.ai workflow. The QuintaDB API covers calls such as list fields and create a field.

- List fields
- Create a field
- Update a field

### Records

Read, create, update, and delete records in QuintaDB from any Tray.ai workflow. The QuintaDB API covers calls such as list records and get a record.

- List records
- Get a record
- Create a record

### Files

Read and create files in QuintaDB from any Tray.ai workflow. The QuintaDB API covers calls such as upload a file and get a file URL.

- Upload a file
- Get a file URL

## Challenges Tray.ai solves

### Keeping QuintaDB credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store QuintaDB credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the QuintaDB API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the QuintaDB API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to QuintaDB?

Yes. Tray.ai connects to QuintaDB through the HTTP Connector, which calls the QuintaDB API directly. Any call the QuintaDB API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with QuintaDB?

The QuintaDB API uses an API key in the query string. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated QuintaDB connector?

QuintaDB runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated QuintaDB connector from the QuintaDB API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/