# TheHive integrations: alerts, cases and tasks

> Create an alert, create a case and create a task in a case in TheHive. Connect TheHive to the rest of your security and compliance stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/thehive-integrations/
**Categories:** Security and compliance
**Connects through:** HTTP Connector

## Overview

TheHive is a security incident response platform from StrangeBee where security teams collect alerts, open and work cases, track tasks and record observables during investigations. Tray.ai connects to TheHive through the HTTP Connector, so your workflows can call the TheHive API alongside the rest of your stack.

## Use cases

### Alerts

Read, create, update, and delete alerts in TheHive from any Tray.ai workflow. The TheHive API covers calls such as create an alert and get an alert.

- Create an alert
- Get an alert
- Update an alert

### Cases

Read, create, update, and delete cases in TheHive from any Tray.ai workflow. The TheHive API covers calls such as create a case and get a case.

- Create a case
- Get a case
- Update a case

### Tasks

Read, create, update, and delete tasks in TheHive from any Tray.ai workflow. The TheHive API covers calls such as create a task in a case and get a task.

- Create a task in a case
- Get a task
- Update a task

### Observables

Read, create, and update observables in TheHive from any Tray.ai workflow. The TheHive API covers calls such as add an observable to a case and add an observable to an alert.

- Add an observable to a case
- Add an observable to an alert
- Get an observable

### Comments

Create, update, and delete comments in TheHive from any Tray.ai workflow. The TheHive API covers calls such as add a comment to a case and add a comment to an alert.

- Add a comment to a case
- Add a comment to an alert
- Update a comment

## Challenges Tray.ai solves

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

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

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

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

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