Customer support integrations.

Gleap has 34 native integrations: app builders (Lovable, Replit, v0, Base44), issue trackers (Jira, Linear, GitHub, GitLab, Azure DevOps, ClickUp, Asana, Trello, Shortcut, Notion, awork, Plutio), notifications (Slack, Microsoft Teams, Discord, Email), CRM and billing context (HubSpot, Salesforce, Stripe, Shopify, Chargebee, Lemon Squeezy), support handoff (Zendesk, Help Scout), calls and meetings (Aircall, Calendly), service status (Better Stack), translation (Crowdin), plus Webhooks and Zapier. Telegram connects as a messaging channel, and Bitbucket as a code host for Kai Code. From Team, Kai Support can use MCP servers and 2,000+ apps through Composio as tools, and so can custom agents. Browse the native integrations.

A native integration is built into Gleap for one workflow, such as creating a Jira issue from a ticket or posting to a Slack channel, and is configured in project settings. Zapier uses Gleap ticket events to start a Zap in another app. Composio toolkits are tools an agent can call during a run: Kai Support and custom agents on Team, Pro and Enterprise, subject to the actions you enable and the connected account's permissions. A directory listing is not a connection: each route needs its own authentication and setup.

Yes, in two directions. The Slack integration sends ticket notifications to a channel of your choice, with thread replies, assignee changes and an optional two-way synchronization setting. A Slack channel can also become a support channel on Team, Pro and Enterprise: messages posted there become Gleap tickets and replies from Gleap return to the original thread. See the Slack integration.

Connect Jira through Atlassian, pick the project and issue type, and choose which ticket types are forwarded automatically. A teammate can also send a single ticket from the ticket sidebar. The Jira issue receives the report with its captured context; updates and messages follow. Status changes in Jira appear in the Gleap ticket's history, and Jira comments arrive as internal notes. See the Jira integration.

Yes. The Linear integration creates issues in the team and project you choose, and Linear status changes and comments flow back into the ticket. The GitHub integration creates issues in the repository you select and reports updates back. Both support automatic forwarding by ticket type and manual sends from the ticket.

Yes. Gleap imports your Zendesk contacts and tickets, with their conversations as comments. The same kind of import works for Intercom, Freshdesk and HubSpot. Help center articles import from Intercom, Help Scout, Freshdesk or a CSV file. During a transition, the native Zendesk integration forwards Gleap tickets to a team that still works in Zendesk. For a side-by-side view, read the Gleap and Zendesk comparison.

Yes. The webhook integration sends ticket events (create, update, delete, new message, assignee change) to a callback URL with custom authentication headers. The REST API, documented at docs.gleap.ai, covers tickets, contacts, help center content and more for anything the native integrations do not do.

Yes, in both directions. The Gleap MCP server lets Claude, Codex, Cursor or any MCP client read and act on your Gleap project. In the other direction, Gleap's agents call the MCP servers you connect, such as Linear, GitHub, a database or a custom HTTP server, with tools switched on per agent: Kai Support, Kai Code and custom agents on Team and up.

Yes. On Team, Pro and Enterprise, Kai Support can use tools you add: API calls, MCP servers including 2,000+ apps through Composio, web search and frontend tools. Kai Support answers customers, so switch on only actions that are safe in a customer conversation. Custom agents on Team, Pro and Enterprise use the tools you attach in the same way. What an agent can do depends on the tools, its configuration and the connected account's permissions. Add a teammate decision where the work calls for judgment.

Team, Pro and Enterprise connect every native integration; Starter connects none. Messaging channels such as Slack and Telegram also need Team, and from Team, Kai Support and Kai Code can use MCP servers and 2,000+ apps through Composio as tools. Custom agents are part of Team, Pro and Enterprise. See pricing for the full comparison.

Yes. Users of an app built with Lovable, Replit, v0 or Base44 report bugs from the Gleap widget, and Kai Code connects through the platform's official MCP server or API to ask its agent for the fix. Kai Code can publish if you allow it. See Gleap for vibe-coded apps.

Kai Code works in repositories on GitHub, GitLab.com, Bitbucket Cloud and Azure DevOps. On Kai Code Cloud it opens a pull request, a merge request on GitLab, for your team to review and merge. On the Kai Code Bridge it opens pull requests on GitHub, GitLab, Bitbucket and Azure DevOps. Without a repository, it works on apps built with Lovable, Replit, v0 and Base44 through each platform's agent. Kai Code is part of Team, Pro and Enterprise.

No. A ticket that arrived through Slack, email or an integration can be investigated by Kai Support like any other, and a confirmed bug becomes a coding task for Kai Code. Sending a ticket to Jira or Linear does not start a fix; it hands the work to the team that works there.

Each native integration authenticates with the account you connect and only runs the actions you configure, such as creating issues for selected ticket types. You can disconnect it from project settings at any time. Agent tools are enabled per agent and can be limited to read-only actions. Security and compliance details are in the Gleap Trust Center.

There is no native Make app. A Make scenario can start from Gleap ticket events: the webhook integration delivers them to any endpoint, including a Make webhook. An agent can also call a Make webhook with an API call tool: Kai Support and custom agents on Team and up. Composio's Make toolkit manages Make organizations and teams; it does not run scenarios. For Zapier, Gleap has an app with feedback-created and feedback-updated triggers.

Use webhooks or Zapier for ticket events, the REST API for data, or an MCP server or HTTP API tool for an agent. Tell us about the workflow if you want help choosing the route.