Gleap

Create a new news or changelog entry. REQUIRED: name (string), subject (localized object, e.g. { "en": "What's New" }), and message (localized TipTap document). Do not call without all three required fields.

create_news

Create a new ticket in Gleap. Type and title are required. Use get_ticket_types to see available types and form data structure.

create_ticket

Create a new ticket with an optional initial message in a single step. This is the recommended way to create tickets. Use get_ticket_types first to see available types and their form fields.

create_ticket_with_message

Permanently delete a news or changelog item by ID. This action cannot be undone.

delete_news

Stage a drafted reply in the ticket's dashboard composer for a human to review, edit and send — NOTHING is sent to the customer. The draft appears instantly in the composer of everyone viewing the ticket. IMPORTANT: call this only when staging a draft is explicitly called for — the user asked you to draft a reply, or the Gleap ticket-resolution workflow you are following instructs you to stage the reply in the composer (e.g. a drafted customer reply that was not approved for direct sending). Never draft proactively or as a side effect of an unrelated request. Replaces any existing draft on the ticket (so it can also be used to revise a draft); the draft is cleared automatically once a reply is sent or the team dismisses it in the composer. The text supports Markdown formatting.

draft_reply_to_composer

List/FILTER tickets by structured fields (status, assignee, priority, tags, date range) — NOT free-text; for keyword search use search_tickets instead, and don't call both for the same intent. Returns lightweight summaries (id, title, status + human-readable statusLabel, priority, assignee, tags, AI summary, form data, timestamps, dashboardUrl); call `get_ticket` afterwards for a match whose full content and conversation you need.

find_tickets

List the project's companies (organisations), most recently seen first, optionally filtered by a name search. Each row carries two identifiers: `id` (the Gleap id — what pipeline tools take as recordId) and `companyId` (the external id your app sends via the SDK — what get_company/update_company take). Returns summaries; call get_company for the full record including custom data.

get_companies

Get one company by its external companyId (the identifier your app sends via the SDK — not the Gleap `id`), including address and custom data. To find contacts belonging to it, use get_contacts with the same companyId.

get_company

Retrieve a specific contact by ID from Gleap.

get_contact

Get all tickets associated with a specific contact. Useful for reviewing a customer's support history. Returns lightweight ticket summaries; call `get_ticket` for the full ticket and conversation.

get_contact_tickets

FILTER contacts by structured fields (userId, name, companyId, companyName, email) with pagination — NOT free-text. For keyword search use search_contacts instead; don't call both for the same intent. Returns lightweight summaries (identity fields, company, plan, value, timestamps); call `get_contact` for the full contact including custom data.

get_contacts

Retrieve a specific help center article by ID.

get_help_center_article

Retrieve articles in a help center collection with optional pagination. Returns lightweight summaries (title, description, slug, tags, draft state, timestamps); call `get_help_center_article` for the full localized article content.

get_help_center_articles

Retrieve help center collections from Gleap with optional pagination.

get_help_center_collections

Retrieve all help center collections including subcollections in tree structure.

get_help_center_collections_tree

Retrieve news and changelog items from Gleap with optional pagination. Use withoutChangelogs to filter to news-only items. Returns lightweight summaries (name, subject, type, status, timestamps); call `get_news_item` for the full localized message body.

get_news

Retrieve a specific news or changelog item by ID.

get_news_item

Get one pipeline including its stages (in board order) and its fields. Entry `values` are keyed by each field's `fieldId`; a field's `calculation` (sum/count/average/min/max/filled/empty) is what get_pipeline_stats aggregates for it — fields without one are not aggregated.

get_pipeline

List a pipeline's entries — every record on the pipeline with its stage and field values. Pass stageId to list one stage (board order); omit it to list across all stages with a `total` for pagination. Each entry carries a `record` snapshot (name, plan, value) of its company/contact.

get_pipeline_entries

Get one pipeline entry together with its pipeline (stages and record type) — the full context needed to move it or update its values.

get_pipeline_entry

Per-stage entry counts and field aggregations for a pipeline, plus whole-pipeline totals — e.g. the sum of deal values in each stage. Aggregations cover the fields with a `calculation` configured (see get_pipeline); to aggregate a field without one, list the entries with get_pipeline_entries and compute from their values. Averages in `totals` are true pipeline-wide averages, not an average of the stage averages.

get_pipeline_stats

List the CRM pipelines visible to this connection. Each pipeline holds records of exactly one type (recordType COMPANY or CONTACT) and carries its stages in order — pass a stage `id` as stageId when adding or moving entries. Call get_pipeline for a pipeline's fields (needed for entry values). Only pipelines that are public or explicitly shared with this connection's user are listed, so a pipeline the user expects may be missing because it is private — in Gleap, open the pipeline's settings and make it public or share it.

get_pipelines

Retrieve individual event rows (the raw log the aggregated statistics are computed from) from Gleap. Every filter is ANDed; unset filters are not applied, so a call with only a date range returns every kind of event in that period. Returns up to 10 000 rows, unpaginated and unsorted, with UTC timestamps — narrow the period or add filters rather than paging. Prefer get_statistics_facts / get_statistics_bar_chart when a count or a trend is all you need.

get_raw_data_statistics

Which pipelines a company or contact is on, with its entry (stage and values) in each — e.g. to check whether a company is already in the sales pipeline before adding it.

get_record_pipelines

Retrieve bar chart statistics from Gleap. Use chartType to specify the type of chart data you want.

get_statistics_bar_chart

Retrieve fact-based statistics from Gleap. Use chartType to specify the type of metric you want.

get_statistics_facts

Retrieve list-based statistics from Gleap. Use chartType to specify the type of list data you want.

get_statistics_list

Get responses for a specific survey with pagination. Each response is returned as a lightweight summary; the survey answers are in `formData`. Use `get_survey_summary` for an AI overview.

get_survey_responses

Get an AI-generated summary of survey responses.

get_survey_summary

List available surveys in the project.

get_surveys

Get all teams in the project with their members. Useful for finding the right team to assign a ticket to.

get_teams

Retrieve the full ticket by ID — content, conversation, form data, and all other fields, plus a human-readable `statusLabel` and a `dashboardUrl` deep link. Use this after `find_tickets` when the slim summary isn't enough. If your prompt already contains this ticket's injected context sections (Kai resolution runs inject the full ticket + conversation), do not re-fetch that same ticket — use this for OTHER tickets, e.g. matches from search_tickets/find_tickets.

get_ticket

Get the activity history for a ticket including status changes, assignments, comments, and other events.

get_ticket_activity_log

Get the full conversation history (messages) for a specific ticket in chronological order — user messages, AI bot answers, and human agent replies. Each message includes the visible text as plain text (TipTap/markdown flattened), the author (senderType: user/agent/bot/system, plus the sender id), AI answer signals (answerBot, hasAnswer, and cited sources), attachments, and timestamps. If your prompt already contains this ticket's conversation, call this only to page OLDER history beyond what was injected (skip/limit), never to re-read what you already have.

get_ticket_messages

Get the project's boards (ticket types): each one's custom data attributes (`schema` + `example`, for building formData), its configured status lanes (`statuses`: key + human-readable title + hidden flag), and its dashboard URL segment (`path`). Call this whenever you need to explain, choose, or list ticket statuses — custom lanes have opaque generated keys like `38jd9` whose only readable form is the lane title returned here.

get_ticket_types

Get all support agents and users in the project. Useful for finding who to assign a ticket to.

get_users

List all workflows (workflow-type bots) in the project, both live and draft. Use this for a full inventory. To start a workflow on a ticket use get_workflows_available_for_ticket (only live workflows on a ticket with a contact can be started), then run_ticket_workflow.

get_workflows

List the workflows that can actually be started on a specific ticket — i.e. the exact set run_ticket_workflow accepts. These are the project's live workflows, but only if the ticket has an associated contact; a ticket without a contact returns an empty list (nothing can be started on it).

get_workflows_available_for_ticket

Link two related tickets together for reference.

link_tickets

Merge duplicate tickets into a single target ticket. Source tickets will be closed and linked to the target.

merge_tickets