Gleap

Create a new help center article. REQUIRED: title, description, and content (all localized objects; content = TipTap doc per locale). Optional: isDraft, targetAudience, tags, externalId. Do not call without title, description, and content.

create_help_center_article

Create a new help center collection. REQUIRED: title (localized object, e.g. { "en": "Name" }). Optional: description, iconUrl, parent, externalId, targetAudience. Do not call without title.

create_help_center_collection

Create a single-use link (valid 15 minutes) that uploads ONE image from disk into this Gleap project, for agents that can run a shell command. Run the returned curl command with your file path; its JSON response carries fileUrl. PNG, JPEG, GIF and WebP up to 20 MB. Use fileUrl as coverImageUrl on create_news_draft / update_news_draft or as an image src in TipTap content. Images: upload first (upload_image, or create_image_upload_link for a file on disk), then add a top-level block node { "type": "imageBlock", "attrs": { "src": "<fileUrl>", "width": "100%", "align": "center", "alt": "<description>" } } between paragraphs (never inside one). width is a percentage string, align left|center|right; optional link + target ("_blank") make the image clickable.

create_image_upload_link

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

Save an unpublished news draft in Gleap and return its reviewUrl. Does not publish, schedule, or send. After human approval of the plan, prepare the draft; obtain a separate approval of the completed content before publication in the dashboard. Requires name, localized subject, and localized TipTap message.

create_news_draft

Save an unpublished newsletter draft in Gleap and return its reviewUrl. Does not publish, schedule, or send. After human approval of the plan, prepare the draft; obtain a separate approval of the completed content before publication in the dashboard. Requires name, localized subject, and localized TipTap message. The draft uses the project's default email template (the first in its template list, as the dashboard picks for a new email) unless emailTemplate names another of the project's templates.

create_newsletter_draft

Create an unpublished survey, chat message, banner, info card (modal), checklist, push notification, product tour or tooltip set, with its content, in the shape the dashboard editor writes. Put the content in the block named after the type (survey, chatMessage, banner, modal, checklist, push, productTour, tooltip). Text fields take plain text per locale. Nothing is shown to anyone: set who and when with configure_outbound_targeting, then publish_outbound after the operator approves. Returns reviewUrl.

create_outbound_draft

Create a new ticket in Gleap. Type and title are required. Use get_ticket_types to see available types and form data structure. The ticket counts as created by your team (like the dashboard's New ticket): it is not triaged as a customer report.

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. Archived tickets are left out unless includeArchived is true — set it for reports and complete counts. Returns lightweight summaries (id, title, status + human-readable statusLabel, priority + priorityLabel, 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

Read an email's status, trigger, frequency and audience (targetAudience + conditions), plus its dashboard reviewUrl.

get_email_automation

How to start tracking an event or contact attribute that targeting needs but the project does not have yet: the call for each SDK (JavaScript, iOS, Android, Flutter, React Native) and from a backend, where to place it, and how to verify it arrived. Use it when get_targeting_options finds no fitting event/attribute; hand the snippet to the developer or a coding agent. Reports whether the name is already tracked.

get_event_tracking_guide

Read one feature request by id or ticket number ("#1234"): title, a description excerpt, roadmap status, upvote count and public share link. Use it when an investigation, a teammate or the thread cites a feature request, to confirm it is the customer's need before subscribe_to_feature_request (which takes the same id). Only feature requests of this project resolve. `public: false` means it is tracked but not on the public roadmap yet: no link and no status to share. Repeat `shareUrl` verbatim, never build roadmap URLs yourself.

get_feature_request

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

Read a newsletter draft's full localized content and dashboard reviewUrl.

get_newsletter_draft

List unpublished, fixed, one-time email campaigns. Returns summaries; use get_newsletter_draft for content and reviewUrl.

get_newsletter_drafts

Read one outbound item: its content (survey questions included), its targeting (delivery, trigger, frequency, page rules, audience, schedule) and reviewUrl; optionally delivery statistics.

get_outbound_message

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