Zapier is the answer when the tool you want isn't in Gleap's integration list. A ticket arrives; something happens in a system Gleap has never heard of.
Unlike other integrations, most of the setup happens in Zapier rather than in Gleap. Gleap's side exists mainly to give you the key that Zapier authenticates with.
Add Zapier from Integrations. The page shows a token — copy it.
Open the Gleap app in Zapier and start a Zap.
When Zapier asks to connect your Gleap account, paste that token.
Choose the trigger, and pick which ticket types it should fire for.
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, via whatever Zapier connector it has.
Zapier is a good middle layer and a poor foundation. If you're building something your team depends on, a webhook straight to your own endpoint is faster, has no per-task cost, and fails in ways you can see.
And if the tool is one Gleap integrates with directly, use that instead — the direct integration syncs both ways, where a Zap only pushes.
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 ticket types that don't match what you're testing with.
