An integration connects Gleap to a tool your team already uses, so a ticket doesn't have to be copied by hand into the place where the work actually happens.
They're in your project settings, under Integrations.
It helps to know which kind you're setting up, because they behave differently.
Push tickets out — issue trackers and project tools like JIRA, Linear, GitHub or ClickUp. A ticket in Gleap becomes a task over there, and updates can flow back.
Bring context in — billing and CRM tools like Stripe, Chargebee, Shopify or Salesforce. Nothing is pushed; the customer's data from that system shows up next to the conversation.
Notify or hand off — Slack, Discord, webhooks, Zapier. Something happened in Gleap and somewhere else needs to know.
Pick it from Add new integration. Most connect through the other tool's login screen; a few ask for an API key instead.
Whichever it is, the connection belongs to the account that authorized it. If that person leaves and their account is deactivated, the integration stops working — which is why it's worth connecting the important ones with an account the team owns rather than a personal one.
For the tools that receive tickets, the configuration screen asks two things: where it should land — the board, project or list — and what should be sent.
There's a switch to send tickets automatically, and next to it a picker for which ticket types to include. This is the setting that decides whether your issue tracker is useful or unbearable.
Leave the switch off and you can still push individual tickets by hand, from the ticket itself. For most teams that's the better default: automatic for bugs, manual for everything else.
The trackers aren't one-way. Depending on the tool, a task being updated, closed or commented on can come back to the Gleap ticket, so the person who reported it can be told without anyone watching both systems.
You can connect the same integration several times — two JIRA projects, two Slack channels — and each gets its own name. Name them for where they point ( “JIRA – mobile” ) rather than leaving the default, or the list becomes unreadable once there are four.
Almost always the connection expired or the account behind it lost access. Reconnecting from the integration's settings fixes it, and it's worth checking after anyone changes permissions in the other tool.
