# Hive integrations: actions, projects and labels

> Create an action, create a project and create a label in Hive. Connect Hive to the rest of your operations stack with Tray.ai.

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

## Overview

Hive is a project management tool where teams plan projects, assign and track actions, message each other and run workflows across workspaces. Tray.ai connects to Hive through the HTTP Connector, so your workflows can call the Hive API alongside the rest of your stack.

## Use cases

### Actions

Read, create, update, and delete actions in Hive from any Tray.ai workflow. The Hive API covers calls such as list workspace actions and search actions.

- List workspace actions
- Search actions
- Create an action

### Projects

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

- List projects
- Create a project
- Copy a project

### Users

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

- List users
- Get a user
- Invite a workspace user

### Teams

Read, create, and delete teams in Hive from any Tray.ai workflow. The Hive API covers calls such as list teams and create a team.

- List teams
- Create a team
- Add team members

### Labels

Read, create, update, and delete labels in Hive from any Tray.ai workflow. The Hive API covers calls such as list labels and create a label.

- List labels
- Create a label
- Update a label

### Webhooks

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

- Create a webhook
- Delete a webhook

## Challenges Tray.ai solves

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

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

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

The Hive API uses an API key in a request header and 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 Hive connector?

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