Skip to content
Gleap logo

Connectors / Customer service · HTTP Connector

Automate Gleap with Tray.ai

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

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

See all connectors

What can you do with Gleap on Tray.ai?

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.

  • Create a ticket when a crash is reported in your error monitoring tool.
  • When Gleap sends “Conversation created”, alert the support team in your team chat.
  • When Gleap sends “Conversation closed”, log the conversation on the customer's record in your CRM.
  • Create an article when your product team publishes a new feature in your release notes.
Connects through
HTTP Connector
Authentication
A bearer token
Base URL
https://api.gleap.io/v3

Set it up

Connect Gleap to Tray.ai

Each step uses Gleap's own API details, from its documentation.

Step 1

Save Gleap's API token

Save the token Gleap issues as a Tray.ai authentication. The HTTP Client sends it as a bearer token on every call. The token stays out of the workflow and out of the logs.

Step 2

Point the HTTP Client at the API

Add an HTTP Client step and use https://api.gleap.io/v3 as the base URL. Or paste a cURL example from Gleap's API docs, and Tray.ai fills in the method, URL, and headers.

Step 3

Start with “List tickets”

It's one of 19 documented actions, under Tickets. The response comes back as data the next step can map into your other apps.

Step 4

Start workflows from Gleap events

Give Gleap the URL of a Tray.ai webhook trigger. “Conversation created” can then start a workflow, and so can 4 other events.

What the Gleap API covers

5 resources and 19 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.

Tickets

  • List tickets
  • Search tickets
  • Create a ticket

Sessions

  • List sessions
  • Create a session
  • Update a session
  • Delete a session
  • Search sessions

Messages

  • Create a message
  • Update a message
  • Delete a message
  • Search messages

Articles

  • List articles
  • Create an article
  • Update an article
  • Delete an article

Surveys

  • List surveys
  • Create a survey
  • Export survey responses

Events Gleap can send to a Tray.ai webhook trigger

  • Conversation created
  • Conversation closed
  • Conversation assigned
  • Message created
  • Contact updated

Checked against Gleap's own documentation on 2026-10-22

docs.gleap.ai/documentation/server/api-overview.md

Frequently asked questions

What can a Tray.ai workflow do in Gleap?

+

The Gleap API documents 19 actions across 5 resources (Tickets, Sessions, Messages, Articles, Surveys). For example: List tickets; List sessions; Create a message. A workflow can make any documented call through the HTTP Connector.

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.

Which Gleap events can start a Tray.ai workflow?

+

Gleap sends 5 events to a webhook URL, for example: Conversation created; Conversation closed; Conversation assigned; Message created; Contact updated. A Tray.ai webhook trigger receives them and starts a workflow.

See Gleap working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.