Zapier is the answer when the tool you want isn't in Gleap's connector list. A ticket arrives; something happens in a system Gleap has never heard of. Only project admins can connect it, and it needs the Team plan or higher. Each project takes one Zapier connection.
Unlike other integrations, most of the setup happens in Zapier. Gleap's side gives you the token Zapier signs in with.
Go to Settings → Connectors, pick Integrations and click Connect next to Zapier.
Gleap creates a token and shows it. Copy it.
Open the Gleap app in Zapier and start a Zap.
When Zapier asks to connect your Gleap account, paste the token.
Choose the trigger and the ticket type it should fire for, then finish the Zap in Zapier.
Turning the Zap on registers it with Gleap; turning it off removes it again. That's why the Gleap side has nothing to configure: the Zap itself is the configuration.
A row in a spreadsheet for every bug report, for a team that lives in spreadsheets.
A message in a tool Gleap doesn't integrate with directly.
A record in an internal system, through whatever Zapier connector it has.
Zapier is a good middle layer and a poor foundation. If you're building something your team depends on, the Webhooks connector sends new tickets and updates straight to your own endpoint, with no per-task cost and no extra service in between.
And if the tool is one Gleap connects to directly, use that instead. Issue trackers can also keep a ticket's status in sync, where a Zap only sends data out of Gleap.
Check Zapier's own task history first. It tells you whether nothing arrived or the Zap failed downstream. If nothing arrived, the usual causes are a Zap that's switched off, or a trigger scoped to a ticket type that doesn't match what you're testing with.
