# Baserow integrations: rows, tables and fields

> Create a row, create a table and create a field in Baserow, and start a workflow when Baserow sends “Rows created”.

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

## Overview

Baserow is an open source no-code database where teams build tables, views and apps in the browser, available as a hosted service or self-hosted. Tray.ai connects to Baserow through the HTTP Connector, so your workflows can call the Baserow API alongside the rest of your stack.

## Use cases

### Rows

Read, create, update, and delete rows in Baserow from any Tray.ai workflow. The Baserow API covers calls such as list rows and get a row.

- List rows
- Get a row
- Create a row

### Tables

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

- List tables
- Create a table

### Fields

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

- List fields
- Create a field

### Webhooks

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

- List webhooks
- Create a webhook
- Update a webhook

### Baserow events

Start a Tray.ai workflow the moment something happens in Baserow. Baserow sends events such as rows created and rows updated to a Tray.ai webhook trigger.

- Rows created
- Rows updated
- Rows deleted

## Challenges Tray.ai solves

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

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

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

The Baserow 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 Baserow connector?

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