Build the handoff your team needs when the destination is connected through Zapier. A Gleap feedback event can start a Zap that passes selected information to another application. Zapier connects on the Team, Pro and Enterprise plans.
Choose the event and the result
The Gleap app in Zapier includes feedback-created and feedback-updated triggers. What happens next depends on the destination app and the action you configure in your Zap.
For example, a new bug report could add a row to an intake spreadsheet. Choose the fields the receiving team needs, then test that mapping with a sample report.
Connect your Gleap project
- Add Zapier from your Gleap project’s Integrations settings.
- Copy the project token shown for the connection.
- Connect the Gleap account in Zapier using that token.
- Choose the trigger, ticket types, and destination action; test the Zap before turning it on.
See the Zapier setup guide for the connection flow. If a run fails, Zapier’s task history helps distinguish a missing trigger from a failed downstream action.
Choose the right connection
Check native integrations for a direct workflow your team can use. If you are building the receiver yourself, Gleap webhooks provide another route.
FAQ
Which Gleap plan includes the Zapier integration?
Team, Pro and Enterprise. Starter includes no integrations. See pricing for the plans.
Which Gleap events can start a Zap?
Two triggers in the Gleap app for Zapier: feedback created and feedback updated. You choose the ticket types in Gleap, and the destination app and its action in the Zap.
Should we use Zapier or Gleap webhooks?
Use Zapier when the destination app has a Zapier action and nobody wants to write code. Use webhooks when your own endpoint should receive the events: they also cover deleted tickets, new messages and assignee changes.
