Integration

Gleap integration

Gleap is a customer support and feedback platform. With this API an agent can work the support inbox as your team: list, create, update, assign, snooze, merge, archive and delete tickets, read their history, post replies or internal notes, create and look up contacts and their memory entries, manage companies and their members, run workflows, maintain help center collections and articles, move entries through CRM pipelines, and search the knowledge base or find similar tickets. Not exposed: engagement campaigns (banners, emails, surveys, tours, news), imports and exports, uploads, presence and typing signals, statistics, invitations, and the separate server-to-server Conversations API, which needs a service-account token. Authentication is a project API key (Project Settings, Security, API Key) sent as a Bearer token together with the project id in the Project header; the server API needs the Team plan or higher. Only EU-region projects (api.gleap.io) are reachable: US-region projects use another host.

Connect Gleap How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Gleap.Built from the 65 Gleap tools below, on the connection you add once.

What you can do with Gleap

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Article, 5 operations

create_articleCreate articlePOSTCreates an article in a collection. It stays an unpublished draft unless isDraft is false. content is TipTap JSON.
delete_articleDelete articleDELETEDeletes a help center article.
get_articleGet articleGETGets one help center article; format=markdown or html adds the content converted to that format.
list_articlesList articlesGETLists the articles of a help center collection.
update_articleUpdate articlePUTUpdates a help center article: send only the fields to change. Pass expectedVersion to refuse the update if someone changed the article meanwhile.

Collection, 5 operations

create_collectionCreate collectionPOSTCreates a help center collection; set parent for a sub-collection. Returns the collection with its _id.
delete_collectionDelete collectionDELETEDeletes a help center collection.
get_collectionGet collectionGETGets one help center collection.
list_collectionsList collectionsGETLists help center collections (top level by default; parentId for children or all), with article and sub-collection counts.
update_collectionUpdate collectionPUTUpdates a help center collection: send only the fields to change.

Memory, 5 operations

delete_contact_memoryDelete contact memoryDELETEDeletes one memory entry of a contact.
get_contact_memoryGet contact memoryGETGets one memory entry of a contact, with its content.
list_contact_memoryList contact memoryGETLists the memory entries stored on a contact (names and descriptions; read one with get_contact_memory for its content).
set_contact_memorySet contact memoryPOSTCreates or replaces a memory entry on a contact, keyed by name. Returns ok and the number of entries.
update_contact_memoryUpdate contact memoryPUTReplaces a memory entry of a contact (content, and description: left out it is cleared).

Ticket, 5 operations

create_ticketCreate ticketPOSTCreates a ticket (every field optional): returns the ticket with _id. sourceTicketId creates it from another ticket and links both. A FEATURE_REQUEST duplicate answers 409 unless skipDuplicateCheck is true.
delete_ticketDelete ticketDELETEPermanently deletes a ticket with its duplicates, messages and logs; this cannot be undone. To keep the ticket, use archive_ticket instead.
get_ticketGet ticketGETGets one ticket by id, dashboard number or share token. Returns the full ticket document, whose fields Gleap does not document beyond those list_tickets shows.
list_ticketsList ticketsGETLists tickets of the project: filter by type, status, priority, archived or spam state, sort, and page with limit/skip. Returns tickets (with _id), count and totalCount.
update_ticketUpdate ticketPUTUpdates a ticket: send only the fields to change (title, status, priority, assignee, tags, customData...). Leave a field out to keep its current value.

Company, 4 operations

delete_companyDelete companyDELETEDeletes a company. Contacts keep their companyId, so an SDK that still sends it re-creates the company on the next identify.
get_companyGet companyGETGets the full record of a company by your own companyId.
list_companiesList companiesGETLists companies, most recently seen first, as summaries (companyId, name, plan, value, domain). Page with limit/skip; filter by name with search.
update_companyUpdate companyPUTCreates or updates a company by your own companyId (created on first use). Send only fields to change; tags replace, address and customData merge.

Member, 3 operations

add_company_memberAdd company memberPOSTLinks a contact to a company; migrateTickets also moves its past conversations onto the company.
list_company_membersList company membersGETLists the contacts linked to a company, most recently active first (_id, name, email, userId, avatar, lastActivity).
remove_company_memberRemove company memberDELETEUnlinks a contact from a company.

Message, 3 operations

create_messageCreate messagePOSTPosts a message in a ticket as the authenticated teammate: a customer reply by default, an internal note with isNote. Use markdownComment for the text.
delete_messageDelete messageDELETEPermanently deletes a message and its thread replies; no webhook or event is sent.
list_messagesList messagesGETLists messages, oldest first: pass ticket to read a whole conversation. Thread replies and ticket history are not included (see list_ticket_history). Attachment URLs expire after about a day.

Session, 3 operations

create_contactCreate contactPOSTCreates or updates a contact: with userId it upserts by userId, otherwise by email. Returns the contact with its Gleap _id.
delete_contactDelete contactDELETEPermanently deletes a contact AND every ticket attached to it; no ticket events or webhooks are sent. This cannot be undone.
get_contactGet contactGETGets a contact (session) by its Gleap id. To look up by your own user id, use get_contact_by_user_id.

Entry, 2 operations

add_pipeline_entryAdd pipeline entryPOSTAdds a company or contact to a pipeline stage, optionally with field values. Returns the entry with its _id.
list_pipeline_entriesList pipeline entriesGETLists the entries of one pipeline stage (laneId), in board order. Page with skip/limit.

Message template, 2 operations

get_message_templateGet message templateGETGets one saved reply template with its content.
list_message_templatesList message templatesGETLists the saved reply templates visible to you, filterable by text, visibility or tag.

Pipeline, 2 operations

get_pipelineGet pipelineGETGets one CRM pipeline with its stages (lanes).
list_pipelinesList pipelinesGETLists the CRM pipelines visible to you, with their stages in lanes (pass a lane id as laneId). An API service account sees only public pipelines and those it was added to.

Pipeline entry, 2 operations

delete_pipeline_entryDelete pipeline entryDELETERemoves an entry from a pipeline (the company or contact itself is kept).
get_pipeline_entryGet pipeline entryGETGets one pipeline entry by id, together with its pipeline: returns entry (stage laneId, record, values, dueDate) and pipeline (name and stages).

Search, 2 operations

search_knowledgeSearch knowledgePOSTSearches the knowledge base (help center articles, snippets, websites, news, videos, code) by meaning. Returns up to 10 documents with title, content and url.
search_messagesSearch messagesGETSearches messages of the project by text and returns the matches in hits.

Archive, 1 operation

archive_ticketArchive ticketPUTArchives a ticket. unarchive_ticket brings it back.

Await customer reply, 1 operation

await_customer_replyAwait customer replyPUTParks a ticket as waiting on the customer: archives it until the customer replies, which unarchives it automatically.

By user id, 1 operation

get_contact_by_user_idGet contact by user idGETGets a contact by your own user id (the one sent to the SDK identify call). Answers 404 when no contact has it.

Compose, 1 operation

create_ticket_with_messageCreate ticket with messagePOSTCreates a ticket for a contact (session id or email; a contact is created for an unknown email) and optionally posts a first message, in one call. Returns the ticket.

Count, 1 operation

count_companiesCount companiesGETCounts the companies matching search (all when left out).

Due date, 1 operation

set_pipeline_entry_due_dateSet pipeline entry due datePUTSets or clears the due date of a pipeline entry.

History, 1 operation

list_ticket_historyList ticket historyGETLists the internal history of a ticket (status, assignee, team, priority, type, tag and title changes, workflow starts, handoffs), oldest first. Entries are kept 180 days.

Link, 1 operation

link_ticketLink ticketPUTLinks two tickets both ways. Linking a regular ticket to a tracker ticket also archives the regular ticket. Linking an already linked pair does nothing.

Merge, 1 operation

merge_ticketsMerge ticketsPUTMerges tickets into a main ticket (targetTicketId, or a new one with shouldCreateNewTicket): merged tickets are archived and linked. Returns the main ticket.

Move, 1 operation

move_pipeline_entryMove pipeline entryPUTMoves a pipeline entry to another stage (laneId).

Property, 1 operation

list_pipeline_propertiesList pipeline propertiesGETLists the fields of a pipeline in column order: ENTRY fields are the keys entry values accept, RECORD fields write through to the company or contact.

Record value, 1 operation

set_pipeline_entry_record_valuesSet pipeline entry record valuesPUTWrites RECORD field values through a pipeline entry to its company or contact.

Resubscribe, 1 operation

resubscribe_contactResubscribe contactPUTResubscribes a contact that was unsubscribed.

Similar ticket, 1 operation

find_similar_ticketsFind similar ticketsPOSTFinds tickets similar to a text by vector search (similarity at least 0.3). Useful to detect duplicates before creating a ticket.

Snooze, 1 operation

snooze_ticketSnooze ticketPUTSnoozes a ticket for duration seconds: status becomes SNOOZED until it reopens automatically when the snooze expires.

Spam, 1 operation

mark_ticket_as_spamMark ticket as spamPUTMarks a ticket and its duplicates as spam, archives it and BLOCKS the contact (future tickets auto-flagged, emails dropped). Undo with unarchive_ticket.

Team, 1 operation

list_teamsList teamsGETLists the teams of the project, with their members and assignment settings. Use a team _id as processingTeam on tickets.

Unarchive, 1 operation

unarchive_ticketUnarchive ticketPUTUnarchives a ticket. On a spam ticket this is "Not spam": it clears the spam flag and unblocks the contact.

Unlink, 1 operation

unlink_ticketUnlink ticketPUTRemoves the link between two tickets.

Unsubscribe, 1 operation

unsubscribe_contactsUnsubscribe contactsPOSTUnsubscribes contacts matching each entry's email or userId. Always answers success: true, whether or not contacts were found.

Value, 1 operation

set_pipeline_entry_valuesSet pipeline entry valuesPUTSets field values on a pipeline entry; sent keys are merged.

Workflow, 1 operation

run_ticket_workflowRun ticket workflowPOSTRuns a Gleap workflow on a ticket.

Use Gleap from Claude Code, Cursor or Codex

Connect Gleap in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Gleap operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Gleap

Create your workspace
Sign up free. Nothing to install.
Connect Gleap once
Add your Gleap connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.