Resources · Zapier integration

Leiga Zapier integrationAutomate Leiga with Zapier.

The Leiga Zapier integration gives you 3 triggers, 1 action and 0 searches. Zapier hears about every issue created, updated or deleted in Leiga as it happens, and it can open new issues there from the other tools your team already works in.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Leiga Zapier integration actually does

Leiga is project management software built for agile teams, organised around issues. On Zapier it does one thing well: it reports every issue that is created, changed or deleted, the instant it happens, and it accepts new issues sent from any other app.

Three results come back again and again. A chat message as soon as an issue is opened: New Issue fires the moment someone creates one, and the team sees it without refreshing the board. Issues opened from wherever requests arrive: Create Issue turns a form answer or a spreadsheet row into a Leiga issue, with a summary and a status. A trace of every change and every deletion: Updated Issue and Deleted Issue feed a log in your spreadsheet, so nothing disappears without a record.

What Zapier does not do for Leiga: there is no search step, so a Zap cannot look up an existing issue before acting on it. There is no action to update or delete an issue either; Create Issue is the only way Zapier writes into Leiga. The good news is on timing: all three triggers are instant, so the interval of your plan never slows them down.

If you are comparing platforms for this kind of workflow, open our Make vs Zapier comparison or see our Zapier review.

Vocabulary

Zapier vocabulary in one minute

Six words carry this page. Here they are once, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Leiga has three, all about issues.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like opening a Leiga issue.
Task
The unit Zapier bills: one action your Zap completes successfully. The figure on your plan is a count of those.
Polling vs instant
Polling: Zapier checks the app on a timer. Instant: the app tells Zapier itself, the moment it happens. All Leiga triggers are instant.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Cost

What Leiga really costs you on Zapier

Leiga is not a premium app, so it runs from the free plan. What you spend is tasks, and only successful actions produce them.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, two-step Zaps only
  • TriggerNever counted, and instant on every plan
  • Failed actionNot counted

The trigger never costs a task, whether it is a new, updated or deleted issue. Each action that completes counts one; a failed one does not. The free plan gives you 100 tasks a month and two-step Zaps only: one trigger, one action. A new issue posted in a chat fits. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below does not apply here: Leiga triggers are instant on every plan.

Connect

Connect your Leiga account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Leiga account linked to Zapier once, then reused by every Leiga step of every Zap.

  2. 02

    Pick Leiga in the dialog

    Search for Leiga in the dialog, select it and click Add connection. You need a Leiga account, plus access to the projects and issues you do not own but want the Zap to reach.

  3. 03

    Sign in and grant access

    A new tab opens on Leiga. Sign in there, then grant Zapier access to the account. Back in Zapier, the connection appears in the list, ready for the three triggers and the action.

First Zap

Your first Zap: tell the team about each new Leiga issue

GoalEvery new issue opened in Leiga posts a message in the team chat at once, filtered so only the issues that concern the channel show up.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose Leiga and New Issue as the event, then select your connection. The editor shows a lightning bolt: this trigger is instant.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent issues of the account, so pick one with a real summary to map the next steps.

  3. 03

    Add the filter

    Click the plus icon and choose Filter. Fill the three boxes: the issue field to look at, the rule, and the value to compare with. On a text field, use a text rule.

  4. 04

    Add the chat message

    Add your team chat with a send-message action and place the issue details your team needs in the text. This is the step that costs a task, one per message.

  5. 05

    Test and publish

    Test each step and read what came back, then click Publish. With the filter it is a multi-step Zap, so it needs a paid plan.

Triggers

The 3 Leiga triggers

3 events start a Zap when something happens in Leiga, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Issue

Instant trigger

In Zapier“Triggers when there is a new issue in Leiga.”

Starts the Zap as soon as someone opens an issue in Leiga, and hands that issue to the following steps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the team wants a ping in its chat, or a row in a tracking sheet, for each new piece of work entering the board.
Watch out
do not pair it with Create Issue on the same account without a filter, or each issue the Zap opens sets it off again.
2

Deleted Issue

Instant trigger

In Zapier“Triggers when an issue is deleted in Leiga.”

Reacts when an issue is removed from Leiga, so a deletion leaves a trace somewhere else instead of vanishing quietly.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a lead wants to know when work leaves the board, or a log must record every removal for later review.
Watch out
the issue no longer exists in Leiga by the time the Zap runs, so write down what you need at that step.
3

Updated Issue

Instant trigger

In Zapier“Triggers when an issue is updated in Leiga.”

Fires each time an existing issue is changed in Leiga, which makes it the busiest of the three on an active board.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you track how issues move, for instance to report each change in a shared sheet the moment it happens.
Watch out
every edit counts as a new event, so a filter keeps the Zap from spending a task on minor changes.
Actions

The Leiga action

Leiga gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Issue

Action

In Zapier“Creates an issue in Leiga.”

Opens a new issue in Leiga from whatever another app sends, with at least a summary and a status name.

When to use it
requests come in through a form, an email tool or a spreadsheet, and you want each one on the Leiga board without retyping.
Watch out
both fields are required, so a record arriving without a status name stops at this step.
When it breaks

When the Leiga Zap breaks

Zapier attaches no help article to Leiga, and no rate limit specific to the app is documented. The usual failures come from how Zapier itself works.

These four cases cover what goes wrong most with instant triggers and an action on the same issues. When a Zap stops and you cannot see why, open our Zapier troubleshooting guide.

  • The Zap keeps opening issues

    A Zap that creates issues in Leiga while New Issue watches the same account sets itself off again and again, and burns through your tasks fast.

  • Old issues are never sent

    A Zap only reacts to what happens after it is switched on. Issues already on the board are not picked up; moving that backlog is a separate job.

  • A bulk change gets held back

    When a trigger suddenly sends a huge batch, after an import or a migration, Zapier's flood protection can hold the run back instead of firing on all of it.

  • The filter never lets anything through

    Filter rules are typed: a text rule only works on text, a number rule only on numbers. Picking the wrong type is why a filter stays shut.
Need help

Need help automating Leiga with Zapier?

A person reads every message.

FAQ

Leiga Zapier integration: frequent questions

01Is the Leiga Zapier integration free?
Yes, as long as each Zap stays at two steps. Leiga is not a premium app, so the free plan accepts it, with 100 tasks a month. Posting each new Leiga issue in your team chat is two steps and costs nothing. Adding a filter so only some issues reach the channel, or a second action after the first, makes the Zap multi-step, and that needs a paid plan. Count your steps before you build.
02How many tasks does a Leiga Zap use?
One per action that succeeds, and nothing for the trigger. A Zap that posts each new issue in a chat and also logs it in a spreadsheet spends two tasks per issue. A failed action is not counted. Updated Issue deserves attention: it fires on every edit, so on a busy board it can run very often. A filter in front of the action keeps the bill down, at the cost of a paid plan.
03Does Leiga trigger Zapier in real time?
Yes. New Issue, Updated Issue and Deleted Issue are all instant triggers: Leiga tells Zapier the moment the event happens, and the Zap starts straight away. That holds on every plan, the free one included, so the interval grid of the plans does not apply. The editor marks these triggers with a lightning bolt. This type is decided by the app itself and cannot be changed from the editor, so there is nothing to tune on your side.
04What does it take to connect Leiga to Zapier?
A Leiga account, and access to any projects and issues you do not own but want the Zap to reach. Open the Apps page in Zapier, click + Add connection, pick Leiga, click Add connection, then sign in to Leiga in the tab that opens and grant access. The connection is saved once, and every Leiga step in every Zap reuses it, with nothing to redo for the next Zap you build on the same account.
05Why does Create Issue stop on the status?
Because Status Name is one of its two required fields, with Summary. Many forms and spreadsheets have no column for a status, so the value is simply missing and the issue cannot be created. Before mapping, check that the source always carries something for both fields. Then test the step once with a real record and read what came back before you publish, so a gap shows up during the build rather than in production.
06What if the Leiga operation you need is not listed?
Then Zapier cannot do it for Leiga today, and no setting will unlock it. The list on this page is the full one the editor shows: three triggers on issues, one action that creates them, and no search. Updating or deleting an issue from a Zap is not on it. A common route is to let Zapier handle the alerts and do the rest by hand, or to compare what other automation platforms offer for Leiga.
07Zapier, Make or n8n for Leiga?
It depends on your criteria, not on a ranking. Zapier connects quickly, its Leiga triggers are instant on every plan, and the free plan covers a two-step Zap such as a chat alert on new issues. Its limits here are a single action and no search step. Make and n8n are built differently, and their own Leiga coverage has to be checked app by app. Weigh setup time, cost per run and the number of steps each Zap needs.
Same platform

Other docs you might need on this stack.

Browse all integrations