# Chekhub integrations: tickets, assets and elements

> Create a ticket, create an asset and create an element in Chekhub. Connect Chekhub to the rest of your operations stack with Tray.ai.

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

## Overview

Chekhub is an operations management platform for mission-critical facilities, tracking tickets, assets, locations and field teams. Tray.ai connects to Chekhub through the HTTP Connector, so your workflows can call the Chekhub API alongside the rest of your stack.

## Use cases

### Tickets

Read and create tickets in Chekhub from any Tray.ai workflow. The Chekhub API covers calls such as list tickets and get a ticket.

- List tickets
- Get a ticket
- Create a ticket

### Assets

Read, create, and update assets in Chekhub from any Tray.ai workflow. The Chekhub API covers calls such as list assets and get an asset.

- List assets
- Get an asset
- Create an asset

### Elements

Read, create, and update elements in Chekhub from any Tray.ai workflow. The Chekhub API covers calls such as list elements and create an element.

- List elements
- Create an element
- Update an element

### Comments

Read, create, update, and delete comments in Chekhub from any Tray.ai workflow. The Chekhub API covers calls such as list comments and create a comment.

- List comments
- Create a comment
- Update a comment

### Notes

Read, create, update, and delete notes in Chekhub from any Tray.ai workflow. The Chekhub API covers calls such as list notes and create a note.

- List notes
- Create a note
- Update a note

### Members

Read members in Chekhub from any Tray.ai workflow. The Chekhub API covers calls such as list members and get a member.

- List members
- Get a member

## Challenges Tray.ai solves

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

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

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

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

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