---
title: "Connect Zapier"
description: "Start Zaps from new Gleap tickets and updates, so tickets reach apps Gleap has no direct integration with."
url: https://help.gleap.ai/fr/articles/359-connect-zapier
collection: "Apps and integrations"
updated: 2026-11-16
language: fr
alternates: [en]
---

# Connect Zapier

Start Zaps from new Gleap tickets and updates, so tickets reach apps Gleap has no direct integration with.

Zapier is the answer when the tool you want isn't in **Settings → Apps**. A ticket arrives; something happens in a system Gleap has never heard of. Only project admins can connect it, and it needs the Growth plan or higher (Team on older plans). Each project takes one Zapier connection.

### Connect it

Unlike other integrations, most of the setup happens in Zapier. Gleap's side gives you the token Zapier signs in with.

1.  Open **Settings → Apps → Add app**, search for the service and open its tile.
    
2.  After **Continue with Zapier**, choose **Create API key**. Gleap then shows the token; copy it for Zapier.
    
3.  Open the Gleap app in Zapier and start a Zap.
    
4.  When Zapier asks to connect your Gleap account, paste the token.
    
5.  Choose the trigger and the ticket type it should fire for, then finish the Zap in Zapier.
    

![Zapier Create API key step before any key is generated in the Pied Piper demo project.](https://staticfiles.gleap.io/p613b5dd730aed737108f87ab/g4U7YXjA3a8dPg5lqTqsbyENOOeFbXiLiugLGzWqKmfEBt7o01xNJnJoYyJjn4lpwhBwLMYlXKY.png)

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.

> **Warning:** The token is a credential for your project. Treat it like a password and don't paste it into a shared document. If it leaks, disconnect Zapier in Gleap and connect it again: that removes the old token and creates a new one, and your Zaps need to be reconnected with it.

### What people build with it

-   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.
    

### When to use something else

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. Jira and Linear also send status changes and comments back to the ticket, where a Zap only sends data out of Gleap.

### When a Zap stops firing

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.

### Related

-   [Browse every integration and what it does](https://help.gleap.ai/en/articles/351-browse-every-integration-and-what-it-does.md)
    
-   [Send tickets to an issue tracker or Slack](https://help.gleap.ai/en/articles/350-send-tickets-to-an-issue-tracker-or-slack.md)
    
-   [Call your own API from a workflow](https://help.gleap.ai/en/articles/314-call-your-own-api-from-a-workflow.md)
