# Gleap integrations: tickets, sessions and messages

> Create a ticket, create a session and create a message in Gleap, and start a workflow when Gleap sends “Conversation created”.

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

## Overview

Gleap is a customer support and feedback platform for apps and websites, combining live chat, bug reporting, help center articles, surveys and product tours. Tray.ai connects to Gleap through the HTTP Connector, so your workflows can call the Gleap API alongside the rest of your stack.

## Use cases

### Tickets

Read and create tickets in Gleap from any Tray.ai workflow. The Gleap API covers calls such as list tickets and search tickets.

- List tickets
- Search tickets
- Create a ticket

### Sessions

Read, create, update, and delete sessions in Gleap from any Tray.ai workflow. The Gleap API covers calls such as list sessions and create a session.

- List sessions
- Create a session
- Update a session

### Messages

Read, create, update, and delete messages in Gleap from any Tray.ai workflow. The Gleap API covers calls such as create a message and update a message.

- Create a message
- Update a message
- Delete a message

### Articles

Read, create, update, and delete articles in Gleap from any Tray.ai workflow. The Gleap API covers calls such as list articles and create an article.

- List articles
- Create an article
- Update an article

### Surveys

Read and create surveys in Gleap from any Tray.ai workflow. The Gleap API covers calls such as list surveys and create a survey.

- List surveys
- Create a survey
- Export survey responses

### Gleap events

Start a Tray.ai workflow the moment something happens in Gleap. Gleap sends events such as conversation created and conversation closed to a Tray.ai webhook trigger.

- Conversation created
- Conversation closed
- Conversation assigned

## Challenges Tray.ai solves

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

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

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

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

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