# Blue integrations: records and custom fields

> Create a record and create a custom field in Blue, and start a workflow when Blue sends “Record created”.

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

## Overview

Blue is a process management platform where teams track work as records in workspaces, with lists, custom fields, assignees, automations and comments. Tray.ai connects to Blue through the HTTP Connector, so your workflows can call the Blue API alongside the rest of your stack.

## Use cases

### Workspaces

Read, create, update, and delete workspaces in Blue from any Tray.ai workflow. The Blue API covers calls such as create a workspace and list workspaces.

- Create a workspace
- List workspaces
- Rename a workspace

### Records

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

- Create a record
- List records
- Update a record

### Custom fields

Read, create, update, and delete custom fields in Blue from any Tray.ai workflow. The Blue API covers calls such as list custom fields and create a custom field.

- List custom fields
- Create a custom field
- Edit a custom field

### Users

Read, create, and delete users in Blue from any Tray.ai workflow. The Blue API covers calls such as invite a user and list users.

- Invite a user
- List users
- Remove a user

### Blue events

Start a Tray.ai workflow the moment something happens in Blue. Blue sends events such as record created and record deleted to a Tray.ai webhook trigger.

- Record created
- Record deleted
- Record moved

## Challenges Tray.ai solves

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

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

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

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

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