# Retable integrations: projects and retables

> Create a project, create a retable and add columns in Retable. Connect Retable to the rest of your data and analytics stack with Tray.ai.

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

## Overview

Retable is an online spreadsheet and database tool where teams organise data into workspaces, projects and tables, then share, search and collaborate on rows. Tray.ai connects to Retable through the HTTP Connector, so your workflows can call the Retable API alongside the rest of your stack.

## Use cases

### Workspaces

Read and create workspaces in Retable from any Tray.ai workflow. The Retable API covers calls such as list workspaces and get a workspace.

- List workspaces
- Get a workspace
- Create a workspace

### Projects

Read and create projects in Retable from any Tray.ai workflow. The Retable API covers calls such as list projects and get a project.

- List projects
- Get a project
- Create a project

### Retables

Read and create retables in Retable from any Tray.ai workflow. The Retable API covers calls such as get a retable and create a retable.

- Get a retable
- Create a retable
- Search a column

### Columns

Create and delete columns in Retable from any Tray.ai workflow. The Retable API covers calls such as add columns and delete columns.

- Add columns
- Delete columns

### Rows

Read, update, and delete rows in Retable from any Tray.ai workflow. The Retable API covers calls such as list rows and insert rows.

- List rows
- Insert rows
- Update rows

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated Retable connector?

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