# Hiver integrations: inboxes and tags

> Create a tag and create a shared draft in Hiver. Connect Hiver to the rest of your customer service stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/hiver-integrations/
**Categories:** Customer service
**Connects through:** HTTP Connector

## Overview

Hiver is a shared inbox and help desk that runs inside Gmail, letting teams assign, tag, and track customer emails together. Tray.ai connects to Hiver through the HTTP Connector, so your workflows can call the Hiver API alongside the rest of your stack.

## Use cases

### Inboxes

Read inboxes in Hiver from any Tray.ai workflow. The Hiver API covers calls such as list inboxes and get an inbox.

- List inboxes
- Get an inbox
- List inbox users

### Tags

Read and create tags in Hiver from any Tray.ai workflow. The Hiver API covers calls such as get inbox tags and search inbox tags.

- Get inbox tags
- Search inbox tags
- Create a tag

### Conversations

Read, create, and update conversations in Hiver from any Tray.ai workflow. The Hiver API covers calls such as list conversations and get a conversation.

- List conversations
- Get a conversation
- Update a conversation

## Challenges Tray.ai solves

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

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

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

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

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