Resources · Zapier integration

Limpi Zapier integrationAutomate Limpi with Zapier.

The Limpi Zapier integration gives you 1 trigger, 2 actions and 2 searches. Enough to start a website audit from another tool, spot every new audit, pull a finished report or cancel a run, without opening Limpi each time.

Beta app Zapier still marks this integration as beta.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Limpi Zapier integration actually does for you

Limpi checks a public website for SEO and GEO problems and hands back recommendations you can act on. Hooked to Zapier, those audits stop being something you launch by hand: another app starts them, Zapier notices when one is created, and the report can travel to wherever your team reads things. Five operations cover it, and Limpi works on the free plan.

An audit that starts itself. Someone fills in a form with their site address, and Create Audit launches the audit on that URL. The form's submission ID goes into the Request Reference field, so a retry by Zapier never produces a duplicate.

A report you don't have to fetch. Once an audit is finished, Get Audit Report picks up its public report from the Audit ID, ready for the next step of your Zap to pass along.

A run you can stop. When an audit went out by mistake, Cancel Audit asks Limpi to stop it, as long as the audit can still be cancelled.

Now the honest part. There is no instant trigger here: New Audit is checked on a timer, so nothing lands the very moment it happens. There is no trigger for a finished audit either, and no action to change or delete one. Zapier also flags this app as beta, so expect it to move. If you are weighing platforms before you commit, see our Zapier review.

Vocabulary

Zapier words you will meet on this page

Eight terms, each in plain words. Once explained, they are used as is.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it.
Action
What the Zap does once it has started: the step that writes, sends or changes something on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant trigger is reported by the app itself the moment it happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Connection
Your Limpi account linked to Zapier once, then reused by every step of every Zap that touches Limpi.
Cost

What a Limpi Zap really costs

Zapier bills tasks, and only some steps produce them. Watching for new Limpi audits never costs a thing.

  • Premium appNo, Limpi runs on the free plan (beta)
  • Free plan100 tasks a month, two-step Zaps
  • Trigger and checksNever billed
  • Failed actionNot billed

The New Audit trigger is free however often Zapier checks. Each action that goes through counts as one task, so a Zap with Create Audit plus a step that posts the result eats two. An action that fails is not charged. The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. Add a filter or a search like Find Audit by ID and the Zap becomes multi-step, which needs a paid plan.

Connect

Connect Limpi to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. You need a Limpi account first, plus access to any audits you did not create yourself and want the Zap to touch.

  2. 02

    Find Limpi

    Type Limpi in the search box of the dialog and pick it from the results. Then click Add connection, which opens a new browser tab where Limpi asks you to sign in.

  3. 03

    Sign in and allow access

    Log into Limpi in that tab and grant Zapier access to the account. The connection is saved once, and every Limpi step you add later can pick it from its account menu.

First Zap

Your first Zap: announce every new Limpi audit

GoalEach new Limpi audit that meets your condition is posted in your team chat, so everyone sees which site is being audited and nobody launches it twice.

  1. 01

    Start with New Audit

    Create a Zap, pick Limpi as the trigger app and New Audit as the event, then choose your connection. Test it: Zapier brings back the three most recent audits so you map from a real one.

  2. 02

    Add a filter

    Click the plus icon and add Filter. Fill its three boxes: the audit field to look at, the rule, and the value to compare with. Pick a text rule for text, or the filter never passes.

  3. 03

    Post the message

    Add a step in your team chat that sends a message naming the audited URL and its Audit ID. With a filter and this step, the Zap is multi-step, so it needs a paid plan.

  4. 04

    Test, then publish

    Run each step once and read what came back. When the message looks right, publish the Zap to switch it on. Only audits created after that moment will start it.

Triggers

The Limpi trigger

1 event starts a Zap when something happens in Limpi. Zapier checks for them at the interval your plan allows.

1

New Audit

Polling trigger

In Zapier“Triggers when a new Limpi audit is created.”

This one starts your Zap whenever a fresh audit shows up in your Limpi account, whether you launched it in Limpi or another Zap did. Each run hands the next steps the details of that audit, including the Audit ID the searches and Cancel Audit expect.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
log every audit your team launches in a shared sheet, so nobody starts the same site twice.
Watch out
it reports an audit when it is created, not when it is finished. The public report only exists for a completed audit.
Actions

Limpi actions

Limpi gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Cancel Audit

Action

In Zapier“Requests cancellation of a cancellable Limpi audit.”

Asks Limpi to stop an audit that is still cancellable. All it needs is the Audit ID, which usually comes from New Audit or from a Create Audit step earlier in the Zap.

When to use it
after a filter that catches audits launched on the wrong address.
Watch out
this is a request, and an audit that can no longer be cancelled will not stop.
2

Create Audit

Action

In Zapier“Starts a new Limpi SEO & GEO audit for a website.”

Launches a new SEO and GEO audit on the public website you point it to. Website URL takes the address; Request Reference takes a unique ID from your trigger.

When to use it
a lead leaves their site address in a form and you want the audit running before anyone reads the entry.
Watch out
reuse the same reference for two genuine audits and Limpi treats the second as a retry.
Searches

Limpi searches

2 search steps look for data that already exists in Limpi, so a later step can use it.

A search step looks up an audit that already exists and passes what it found down the Zap. In the editor, Limpi's two searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not what you expected.

1

Find Audit by ID

Search

In Zapier“Finds one Limpi audit from its Audit ID.”

Pulls up one specific Limpi audit when you already hold its Audit ID from another step, so later steps can read its details.

When to use it
a later step needs the audit's current state rather than what the trigger saw at creation.
Watch out
it only works with an exact Audit ID, never with a website address.
2

Get Audit Report

Search

In Zapier“Gets the public report for a completed Limpi audit.”

Fetches the public report of an audit once Limpi has finished it, ready to be shared or stored by the next step.

When to use it
send the report link to the person who asked for the audit.
Watch out
it only covers completed audits, while New Audit reports one that has just been created.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that depend on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Limpi offers no such variant, so you will not see it on these two searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When a Limpi Zap breaks

Zapier attaches no help article to Limpi, and no app-specific limit is documented. What breaks comes from how Zapier itself works.

  • Old audits are not picked up

    A Zap only reacts to what happens after you switch it on. Audits created before that stay out, and moving them is a separate job.

  • A Zap that keeps restarting

    If a Zap built on New Audit also runs Create Audit, every audit it creates sets it off again, and your task count drains fast.

  • A sudden flood is held back

    When the trigger suddenly returns a huge batch, after a bulk import for instance, Zapier's flood protection can hold those runs back.

  • The same audit never fires twice

    Zapier remembers what it has already seen on a polling trigger, so a New Audit it handled once will not restart the Zap.
Need help

Need help automating Limpi with Zapier?

A person reads every message.

FAQ

Limpi Zapier integration: common questions

01Is the Limpi Zapier integration free?
Yes, as long as your Zap stays at two steps. Limpi is not a premium app, so it runs on Zapier's free plan, which gives you 100 tasks a month and Zaps made of one trigger and one action. A form that feeds Create Audit fits inside that. Add a filter, a search or a second action and the Zap turns multi-step, which needs a paid plan. Zapier also marks Limpi as beta, so its set of operations may still change over time.
02How many tasks does a Limpi Zap use?
One per action that succeeds, and nothing else. The New Audit trigger never costs a task, however often Zapier checks Limpi for new audits, and the search for new data is free too. A Zap that runs Create Audit once uses one task per run; add a message step after it and each run costs two. If Create Audit or Cancel Audit fails, that attempt is not counted against your plan, so a broken step does not quietly eat your monthly allowance.
03Does Limpi trigger Zaps in real time?
No. New Audit is a polling trigger: Zapier asks Limpi for new audits at regular intervals, and the interval depends on your plan. That is every 15 minutes on Free, 2 on Professional and 1 on Team or Enterprise. The type comes from the way Limpi built its side of the integration and cannot be switched to instant from the editor. On paid plans you can change how often the check runs, and you can also start a check by hand from the editor when you are testing.
04What does it take to connect Limpi to Zapier?
A Limpi account, plus access to any audits you did not create yourself but want the Zap to touch. The connection starts from the Apps page of your Zapier account with + Add connection. You search for Limpi in the dialog, click Add connection, sign in through the tab that opens and grant Zapier access to the account. Once saved, every Limpi step in every Zap reuses that same connection, so there is nothing to set up again when you build the next one.
05Why does Create Audit ask for a Request Reference?
Because it stops duplicates. Zapier reuses that value whenever it retries a step, so Limpi recognises the retry and does not start the same audit twice. Pick a stable unique ID from the step that starts your Zap, such as an order ID, a form submission ID or a contact ID. Each genuine audit needs its own value, otherwise Limpi takes the second one for a retry and never runs it. Map it from the trigger step rather than typing a fixed value, so that every run carries its own reference.
06What if the Limpi operation you need is not listed?
Then the Zap cannot do it with Limpi as things stand. Zapier currently offers five Limpi operations: New Audit, Create Audit, Cancel Audit, Find Audit by ID and Get Audit Report. There is, for example, no trigger that fires when an audit is finished and no action that edits or deletes an audit. Since the app is in beta, the list is worth checking again on its Zapier page before you build a workflow around a missing piece, rather than counting on it appearing.
07Zapier, Make or n8n for Limpi?
It depends on your criteria rather than on a single winner. Check first whether Limpi exists on the other platform at all, because this page only covers Zapier. Then compare how each one bills: Zapier counts every successful action as a task, and its free plan stops at two-step Zaps. Finally weigh how much logic you need around each audit, since a filter before Cancel Audit or a search for the report makes a Zapier Zap multi-step, and therefore paid.
Same platform

Other docs you might need on this stack.

Browse all integrations