# Fibery integrations: entities, files and schema

> Create an entity, upload a file and create a database in Fibery, and start a workflow when Fibery sends “Entity changed”.

**Canonical page:** https://tray.ai/connectors/fibery-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Fibery is a connected workspace where teams build their own databases for product management, projects, CRM and knowledge, linking records across them. Tray.ai connects to Fibery through the HTTP Connector, so your workflows can call the Fibery API alongside the rest of your stack.

## Use cases

### Entities

Read, create, update, and delete entities in Fibery from any Tray.ai workflow. The Fibery API covers calls such as query entities and create an entity.

- Query entities
- Create an entity
- Update an entity

### Files

Create and update files in Fibery from any Tray.ai workflow. The Fibery API covers calls such as upload a file and attach a file to an entity.

- Upload a file
- Attach a file to an entity

### Schema

Create and update schema in Fibery from any Tray.ai workflow. The Fibery API covers calls such as create a database and add a field.

- Create a database
- Add a field
- Update the workspace schema

### Webhooks

Create and delete webhooks in Fibery from any Tray.ai workflow. The Fibery API covers calls such as create a webhook and delete a webhook.

- Create a webhook
- Delete a webhook

## Challenges Tray.ai solves

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

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

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

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

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