Customer support integrations.
Keep the tools you build with.
34 native integrations, plus webhooks, Zapier and the API. MCP servers and 2,000+ apps through Composio give the agents their tools.
Every connected app, what it does for you and what Kai may do with it.
Every app your team connected, once, and what it does for you. Shared ones work for everyone and every agent; ones with a lock only for the people they name. Open one to choose what it does, what Kai may do with it and who can use it.
Where Gleap sends tickets, bugs and updates for your team.
StripeLumen Inc · Inbox panel, Kai answers billing questionsLumen Inc · Inbox panel, Kai answers billing questions Kai can use
GitHublumen-demo · Kai Code, code knowledge, send ticketslumen-demo · Send tickets Sends ticketsKai can use
SlackLumen · Notifications, agent toolsLumen · Notifications Sends ticketsKai can use
LinearLumen · Send ticketsLumen · Send tickets Sends tickets
JiraTurn tickets into Jira issues and let Kai look up issue status. Connect
LinearTurn tickets into Linear issues and let Kai look up what is planned. Connect
AsanaTurn tickets into Asana tasks. Connect
ClickUpTurn tickets into ClickUp tasks. Connect
ZendeskHand tickets over to Zendesk, or move your help center and conversations to Gleap. Connect
HubSpotSend tickets to HubSpot, let Kai look up contacts and deals, and import your contacts and tickets. Connect -
34 native integrations
Jira, Linear, GitHub, Slack, HubSpot, Stripe and more, connected in project settings.
-
Your own workflows
Webhooks, Zapier and the REST API cover the rest.
-
Tools for the agents
MCP servers and 2,000+ apps through Composio, from Growth.
-
Context travels along
The ticket keeps its evidence on every route.
All integrations
-
Jira Send customer issues to the right Jira project, with the report context attached. -
Linear Bring customer reports into your Linear team, with a clear path from support to engineering. -
GitHub Turn customer bug reports into GitHub issues, and let Kai Code open pull requests in your GitHub repositories. -
Slack Bring customer issues into Slack, or turn a Slack support channel into your Gleap inbox. -
GitLab Send customer bug reports to GitLab issues, and let Kai Code open merge requests in your GitLab repositories.
-
Azure DevOps Create Azure DevOps work items from customer reports, and let Kai Code prepare pull requests in Azure Repos. -
Zendesk Hand customer tickets to a team working in Zendesk, with the original report context. -
HubSpot Create HubSpot tickets from Gleap conversations and route them into the right service pipeline. -
Salesforce Turn Gleap tickets into Salesforce cases for the team managing the customer account. -
Stripe Kai answers billing questions with the customer's real Stripe subscription and invoices, explains charges. -
Microsoft Teams Send Gleap ticket notifications to the Microsoft Teams channel your team already follows. -
Notion Collect customer reports in a Notion database your product team can work from. -
Asana Turn customer reports into Asana tasks in the project and section where your team works. -
Trello Create Trello cards from customer reports and send them straight to the list your team uses. -
ClickUp Bring customer reports into the right ClickUp list, with their context ready for the next team. -
Shortcut Turn customer reports into Shortcut stories in the workflow your engineering team uses. -
Help Scout Create Help Scout conversations from Gleap tickets for a team that answers from a Help Scout mailbox. -
Email Send new tickets to an email address, with a preview and a link to open them in Gleap.
-
Webhooks Send Gleap ticket events to your own endpoint and build the next step in your stack. -
Zapier Use Gleap ticket events to start a Zap and carry customer context into another tool. -
Discord Send customer issue notifications to the Discord channel where your team coordinates work. -
Aircall Start an Aircall conversation from a Gleap contact and keep the follow-up notes with the account. -
Cal.com Kai offers open slots from your Cal.com in the conversation and books the meeting for your customer, with the invite sent right away.
-
Calendly Kai offers free times from your Calendly in the conversation and books the meeting the customer picks, with the invite sent right away. -
Shopify Kai answers where-is-my-order, product and discount questions from your Shopify store, starts returns and exchanges.
-
WooCommerce Kai answers where-is-my-order, product and discount questions from your WooCommerce store and starts returns and exchanges once the customer confirms.
-
Chargebee Kai answers billing questions with the customer's real Chargebee subscription and invoices, explains charges.
-
Paddle Kai answers billing questions with the customer's real Paddle subscription and transactions, explains charges. -
Lemon Squeezy Kai answers license, renewal and billing questions with the customer's real Lemon Squeezy subscription and orders.
-
RevenueCat Kai answers in-app subscription questions with the customer's real RevenueCat subscription and sends the link where they manage it in the App Store or Google.
-
Better Stack Show your Better Stack status page in the Gleap widget and give Kai Support the current service status. -
Crowdin Translate Gleap Help Center articles with Crowdin and bring finished translations back into your knowledge base. -
Replit Install Gleap in your Replit app, collect bug reports with replay and logs, and let Kai Code ask Replit Agent to make the fix your team publishes.
-
awork Send customer reports into awork as tasks, with a defined project, work type, and starting status. -
Lovable Install Gleap in your Lovable app, collect bug reports with replay and logs, and let Kai Code ask Lovable's agent to make the fix your team publishes.
-
Plutio Create Plutio tasks from customer reports in the business and project structure you choose. -
v0 Install Gleap in your v0 app, collect bug reports with replay and logs, and let Kai Code ask v0's agent to make the fix your team publishes.
-
Base44 Install Gleap in your Base44 app, collect bug reports with replay and logs, and let Kai Code ask Base44's AI to make the fix and publish it.
-
Bitbucket Connect Bitbucket repositories to Kai Code, which opens pull requests there for your team to review.
-
Telegram Receive Telegram support conversations in Gleap and reply where your customers started.
-
Basecamp Let a Gleap AI agent turn confirmed bug reports into Basecamp to-dos, add customer evidence as comments and post updates to Campfire.
-
Cursor Let a Gleap AI agent check your Cursor cloud agents and their conversations, so support knows when a fix for a customer is in progress.
-
Delighted Qualtrics shut Delighted down on June 30, 2026, so Gleap AI agents cannot use it anymore; Gleap surveys can take over your NPS program.
-
Doppler Give Kai Code and Gleap AI agents Doppler config logs and secret names, with value reads switched off, to see which setting changed before a bug.
-
Fathom Let a Gleap AI agent read Fathom meeting summaries and transcripts and turn what customers asked for into feature request votes and tasks in Gleap.
-
incident.io Let a Gleap AI agent read live incident.io incidents and updates for support and add the customer impact from Gleap reports to the incident.
-
Loops.so Let Gleap AI agents find Loops.so contacts, update their properties and subscription status and send events to your Loops workflows.
-
Metabase Let Gleap AI agents run saved Metabase questions and search dashboards to answer account and usage questions in support tickets.
No integrations match your search.
Showing 1–48 of 1001 integrations
Issue trackers
A ticket, sent to Jira or Linear.
Or GitHub, GitLab, ClickUp and Asana, with the report's context attached.
See in-app bug reporting
JiraEngineering -
Send from the ticket
One click in the ticket sidebar.
-
Forward automatically
Choose the ticket types that go out by themselves.
-
Updates follow
Updates and messages follow the linked issue.
-
Changes come back
Jira, Linear, GitHub, ClickUp and Trello report changes to the ticket.
Three ways to connect
Connect it your way.
Customer support integrations connect Gleap to the tools you already use. There are 34 native integrations, including Jira, Linear, GitHub, Slack, HubSpot and Stripe, plus webhooks, Zapier and the REST API. From Growth, MCP servers and 2,000+ apps through Composio give Kai Support, Kai Code and custom agents their tools. Integrations come with Growth, at $99 a month billed annually.
- Apps Add app
Every connected app, what it does for you and what Kai may do with it.
All4Kai can use4Sends tickets2Shows in the inbox2ConnectedEvery app your team connected, once, and what it does for you. Shared ones work for everyone and every agent; ones with a lock only for the people they name. Open one to choose what it does, what Kai may do with it and who can use it.
Where Gleap sends tickets, bugs and updates for your team.
Shopifylumen-demo.myshopify.com · Inbox panel, Kai looks up orders, Kai recommends productslumen-demo.myshopify.com · Inbox panel, Kai looks up orders, Kai recommends products Kai can use
StripeLumen Inc · Inbox panel, Kai answers billing questionsLumen Inc · Inbox panel, Kai answers billing questions Kai can use
GitHublumen-demo · Kai Code, code knowledge, send ticketslumen-demo · Send tickets Sends ticketsKai can use
SlackLumen · Notifications, agent toolsLumen · Notifications Sends ticketsKai can use
LinearLumen · Send ticketsLumen · Send tickets Sends tickets More apps that get tickets
JiraTurn tickets into Jira issues and let Kai look up issue status. Connect
LinearTurn tickets into Linear issues and let Kai look up what is planned. Connect
AsanaTurn tickets into Asana tasks. Connect
ClickUpTurn tickets into ClickUp tasks. Connect
ZendeskHand tickets over to Zendesk, or move your help center and conversations to Gleap. Connect
HubSpotSend tickets to HubSpot, let Kai look up contacts and deals, and import your contacts and tickets. Connect Build your ownMCP serverKai uses the tools your own server offers. 2,000+ more appsHubSpot, Notion, Airtable and others, signed in once. Your APIEndpoints Kai calls: base URL and headers once, then one row per endpoint.34 native integrations
Jira, Linear, GitHub, GitLab, Slack, Zendesk, HubSpot, Stripe and more.
Browse native integrations - Webhook URL
Webhooks Not connected https://api.acme.example/gleap/eventsHeadersAuthorizationBearer ••••••••••••Ticket eventsCreateUpdateDeleteSend messageSave - Tools Add tool
The tools Kai Support can use. What it may do with each is set once, on the tool.
Always First answers and deeper investigation.GleapBuilt-in Always on AlwaysLumen API Kai can use it in any conversation AlwaysOnly in deeper investigation Opened once Kai Support takes a closer look at a ticket.Stripe Used by Refunds Only in deeper investigation
Linear Used by Bugs Only in deeper investigation
MCP servers for the agents
From Growth, Kai Support, Kai Code and custom agents use the MCP servers and Composio apps you add.
See the Gleap MCP server - Vibe codingApps on vibe coding platforms Kai Code can fix.LovableKai asks the Lovable agent to make changes · can publish
LumenConnected by LukasConnectedAdd projectLumen Bookingslumen-demo.lovable.appOpen in LovableKai may publish1 projectBuilt with an app builder?
Connect Lovable, Replit, v0 or Base44 once. Kai Code asks the platform's own agent for each fix.
Gleap for vibe-coded apps
Investigated from any channel.
Integration tickets included.
Kai Support investigates the hard tickets that arrived through Slack, email or an integration and returns a verdict with evidence. Confirmed bugs become coding tasks for Kai Code.
Meet Kai SupportQuestions
About integrations
What are customer support integrations?
Customer support integrations connect your help desk to the tools your team already uses, such as an issue tracker, a chat tool, a CRM or a billing system, so a ticket and its context travel between them. Gleap has 34 native integrations, plus webhooks, Zapier, the REST API, MCP servers and 2,000+ apps through Composio.
Which integrations does Gleap have?
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 Growth, Kai Support can use MCP servers and 2,000+ apps through Composio as tools, and so can custom agents.
Browse the native integrations.
With Shopify connected, Kai answers where-is-my-order questions. With Stripe, Chargebee or Lemon Squeezy, it handles AI billing support.
What is the difference between a native integration, Zapier and Composio?
- 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 Growth, 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.
Does Gleap integrate with Slack?
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 Growth, Pro and Enterprise: messages posted there become Gleap tickets and replies from Gleap return to the original thread. See the Slack integration.
How does the Jira integration work?
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.
Does Gleap integrate with Linear and GitHub?
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.
Can we move from Zendesk to Gleap?
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.
All 17 questions
Does Gleap have an API and webhooks?
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.
Does Gleap support MCP?
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 Growth and up.
Can Gleap agents use our other tools?
Yes. On Growth, 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 Growth, 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.
Which plan includes integrations?
Growth, Pro and Enterprise connect every native integration; Hobby connects none. Messaging channels such as Slack and Telegram also need Growth, and from Growth, Kai Support and Kai Code can use MCP servers and 2,000+ apps through Composio as tools.
Custom agents are part of Growth, Pro and Enterprise. See pricing for the full comparison.
Does Gleap integrate with Lovable, Replit, v0 and Base44?
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.
Which code hosts does Kai Code work with?
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 Growth, Pro and Enterprise.
Does an integration change what Kai Support and Kai Code do?
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.
How do integrations handle permissions and data?
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.
Does Gleap work with Make?
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 Growth 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.
What if the tool we need is not listed?
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.
Connect the tools you build with.
7 days free. No credit card needed. 4.6
