# Xata integrations: projects and branches

> Create a project and create a branch in Xata. Connect Xata to the rest of your data and analytics stack with Tray.ai.

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

## Overview

Xata is a managed Postgres platform built around fast database branching, letting teams copy production data safely into isolated branches for testing. Tray.ai connects to Xata through the HTTP Connector, so your workflows can call the Xata API alongside the rest of your stack.

## Use cases

### Projects

Read, create, update, and delete projects in Xata from any Tray.ai workflow. The Xata API covers calls such as list projects and create a project.

- List projects
- Create a project
- Get project details

### Branches

Read, create, and delete branches in Xata from any Tray.ai workflow. The Xata API covers calls such as list branches and create a branch.

- List branches
- Create a branch
- Delete a branch

### Organizations

Read and create organizations in Xata from any Tray.ai workflow. The Xata API covers calls such as list organizations and list organization members.

- List organizations
- List organization members
- Send an invitation

### API keys

Read and create api keys in Xata from any Tray.ai workflow. The Xata API covers calls such as list API keys and create an API key.

- List API keys
- Create an API key

## Challenges Tray.ai solves

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

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

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

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

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