# Fusioo integrations: records, apps and discussions

> Create a record, create a discussion and create a file in Fusioo, and start a workflow when Fusioo sends “Record created”.

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

## Overview

Fusioo is an online database builder where teams create custom apps to track projects, clients, inventory and other records without code. Tray.ai connects to Fusioo through the HTTP Connector, so your workflows can call the Fusioo API alongside the rest of your stack.

## Use cases

### Records

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

- List records
- Get a record
- Create a record

### Apps

Read apps in Fusioo from any Tray.ai workflow. The Fusioo API covers calls such as list apps and get an app.

- List apps
- Get an app

### Discussions

Read, create, and delete discussions in Fusioo from any Tray.ai workflow. The Fusioo API covers calls such as list discussions and create a discussion.

- List discussions
- Create a discussion
- Create a comment

### Files

Read, create, and delete files in Fusioo from any Tray.ai workflow. The Fusioo API covers calls such as get a file and download a file.

- Get a file
- Download a file
- Create a file

### Users

Read users in Fusioo from any Tray.ai workflow. The Fusioo API covers calls such as list users and get a user.

- List users
- Get a user

### Webhooks

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

- List webhooks
- Create a webhook
- Update a webhook

## Challenges Tray.ai solves

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

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

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

The Fusioo API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Fusioo connector?

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