# NocoDB integrations: records, tables and fields

> Create records, create a table and create a field in NocoDB, and start a workflow when NocoDB sends “Record inserted”.

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

## Overview

NocoDB is a no-code database platform for building tables, views, forms, and dashboards, available on NocoDB Cloud or as a self-hosted deployment. Tray.ai connects to NocoDB through the HTTP Connector, so your workflows can call the NocoDB API alongside the rest of your stack.

## Use cases

### Records

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

- List records
- Create records
- Update records

### Tables

Read, create, update, and delete tables in NocoDB from any Tray.ai workflow. The NocoDB API covers calls such as list tables and create a table.

- List tables
- Create a table
- Update a table

### Fields

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

- Create a field
- Update a field
- Delete a field

### Views

Read, create, and delete views in NocoDB from any Tray.ai workflow. The NocoDB API covers calls such as list views and create a view.

- List views
- Create a view
- Delete a view

### Webhooks

Read, create, and delete webhooks in NocoDB from any Tray.ai workflow. The NocoDB API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- Delete a webhook

### Comments

Read and create comments in NocoDB from any Tray.ai workflow. The NocoDB API covers calls such as list comments and create a comment.

- List comments
- Create a comment
- Resolve a comment

## Challenges Tray.ai solves

### Keeping NocoDB 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 NocoDB 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 NocoDB 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 NocoDB 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 NocoDB?

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

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

The NocoDB API uses an API key in a request header and a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated NocoDB connector?

NocoDB runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated NocoDB connector from the NocoDB 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/