# AITable.ai integrations: records, fields and nodes

> Create records, create a field and create a role in AITable.ai. Connect AITable.ai to the rest of your data and analytics stack with Tray.ai.

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

## Overview

AITable.ai is a spreadsheet-style database where teams organise records in datasheets and views, and can build AI chatbots on top of their data. Tray.ai connects to AITable.ai through the HTTP Connector, so your workflows can call the AITable.ai API alongside the rest of your stack.

## Use cases

### Records

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

- Get records
- Create records
- Update records

### Fields

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

- Get fields
- Create a field
- Delete a field

### Nodes

Read nodes in AITable.ai from any Tray.ai workflow. The AITable.ai API covers calls such as list nodes and search nodes.

- List nodes
- Search nodes
- Get node details

### Teams

Read, create, update, and delete teams in AITable.ai from any Tray.ai workflow. The AITable.ai API covers calls such as list teams and create a team.

- List teams
- Create a team
- Update a team

### Roles

Read, create, update, and delete roles in AITable.ai from any Tray.ai workflow. The AITable.ai API covers calls such as list roles and create a role.

- List roles
- Create a role
- Update a role

## Challenges Tray.ai solves

### Keeping AITable.ai 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 AITable.ai 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 AITable.ai 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 AITable.ai 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 AITable.ai?

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

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

The AITable.ai API uses 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 AITable.ai connector?

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