Customer support integrations.

Gleap has 25 native integrations: issue trackers (Jira, Linear, GitHub, Azure DevOps, ClickUp, Asana, Trello, Shortcut, Notion, awork, Plutio), chat and notifications (Slack, Microsoft Teams, Discord, Telegram), CRM and billing context (HubSpot, Salesforce, Stripe, Shopify), support handoff (Zendesk), calls and meetings (Aircall, Calendly), translation (Crowdin), plus Webhooks and Zapier. Custom agents can also use Composio toolkits, with 985 listed in the directory, and any MCP server you connect. 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 a custom agent can call during a run, 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: 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, and status changes in Jira are reported back to the Gleap ticket. 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. Help center articles can be imported from Zendesk, Intercom and HubSpot into the Gleap knowledge base. The native Zendesk integration forwards Gleap tickets to a team that still works in Zendesk during a transition. 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.io, 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, Kai Code, Kai Resolve and custom agents call the MCP servers you connect in settings, such as Linear, GitHub, a database or a custom HTTP server, with tools switched on per agent.

Yes. Custom agents use the tools you attach: MCP servers, Composio toolkits and HTTP API tools you define. 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.

Starter connects Jira, Trello and Slack. Team, Pro and Enterprise connect every native integration. Custom agents, and with them Composio toolkits and MCP tools, are part of Pro and Enterprise. See pricing for the full comparison.

No. A ticket that arrived through Slack, email or an integration can be investigated by Kai Resolve 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.

Gleap has a Zapier app with feedback-created and feedback-updated triggers. There is no Make app today; connect Make, n8n or your own service through the webhook integration, which delivers the same ticket events to any endpoint.

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.