Lumar Zapier integrationAutomate Lumar with Zapier.
The Lumar Zapier integration ties your website crawls to the rest of your tools. It offers 2 triggers and 2 actions: what each one does, what it costs in tasks, how to connect your account and where a Lumar Zap tends to break.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lumar Zapier integration actually does
The integration plugs Lumar, the crawler that audits how a website is built, into Zapier. When a crawl ends or a task appears in Lumar, Zapier can do something for you in another app. It also works the other way round: an event elsewhere can create an SEO project in Lumar or launch a crawl, without anyone opening Lumar.
Three results you can build. First, a crawl that announces itself: Crawl Finished spots the end of a crawl in a chosen project and posts a message where your team already talks, so the people who read the audit learn it is done. Second, projects that set themselves up: a new entry in another tool, a form answer for example, feeds Create SEO Project with a name and a domain. Third, crawls launched on demand: an event in another app calls Run Crawl on an existing project, so the next audit starts from the tool where the change was logged, not from a reminder someone has to act on.
What Zapier does not do for Lumar: it cannot edit or delete a project, stop a crawl or look anything up, since the app has no search step. Both triggers are polling triggers, so a finished crawl is noticed at the next check, not as it ends.
Still choosing a platform? Read the n8n vs Zapier comparison before you build.
Zapier vocabulary in one minute
Seven words come back all over this page. Each one is explained once here, in plain words.
- 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 switched on, Zapier waits for that event and nothing else.
- Action
- What the Zap does once it has started: the step that creates, sends or launches something in an app for you.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant one is reported by the app the moment it happens. Lumar has polling only.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it quietly otherwise.
- Connection
- Your Lumar account linked to Zapier once, then reused by every step of every Zap that works with Lumar.
What a Lumar Zap really costs
Lumar is not a premium app, so it runs on the free plan. Triggers never cost a task, and neither do the checks Zapier makes on Lumar to spot a finished crawl or a new task, however often it looks.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap sizeTwo steps: one trigger, one action
- Premium appNo, works on the free plan
- Lumar triggersBoth checked by polling
Only a successful action is billed. Each Run Crawl or Create SEO Project that goes through is one task, and one that fails costs nothing. A message sent to your team after a crawl is one task too. The free plan stops at two steps, one trigger and one action; a filter or a second action makes the Zap multi-step, which needs a paid plan. The grid below shows how often Zapier checks the two Lumar triggers on each plan.
Connect Lumar to Zapier in three steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Lumar account linked to Zapier once, then reused by every step that needs it.
- 02
Pick Lumar
Type Lumar in the search box of the dialog, select it, then click Add connection. A new tab opens on the Lumar side to finish the link with your own Lumar login.
- 03
Sign in and grant access
Log in to Lumar in that tab and grant Zapier access to your account. You need a Lumar account, plus access to any account or project you do not own yourself and want the Zap to touch.
Your first Zap: hear about the crawls that matter
GoalWhen a crawl finishes in a chosen Lumar project, let only the crawls that match your rule through and send your team a message about them.
- 01
Create the Zap and set the trigger
Start a new Zap, pick Lumar as the app that starts it and
Crawl Finishedas the event. Choose your connection, then the Account and the Project to watch. - 02
Test the trigger
Run the test. Zapier brings back the three most recent finished crawls of that project, so you set up the next steps on a real one.
- 03
Add the filter
Click the plus icon and pick Filter. Fill the three boxes: the field to look at, the rule, and the value. Pick a number rule for a number field.
- 04
Add the message
Add your messaging tool as the action, with its send step, and place the crawl details that came from the trigger into the message.
- 05
Test, then publish
Test each step, then click Publish. The filter makes this a multi-step Zap on a paid plan; only the messages actually sent cost a task.
The 2 Lumar triggers
2 events start a Zap when something happens in Lumar. Zapier checks for them at the interval your plan allows.
Crawl Finished
Polling triggerIn Zapier“Triggers when a new Crawl has finished in the selected Project.”
Starts the Zap when a crawl has finished in the project you select. That is the moment the results are ready to read, so it is the natural point to warn someone, log the crawl or kick off whatever comes next.
Task Created
Polling triggerIn Zapier“Triggers when a new Task is created.”
Fires when a new task is created in your Lumar account. It brings those tasks out of Lumar and into the tool where your team actually tracks its work.
The 2 Lumar actions
Lumar gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create SEO Project
ActionIn Zapier“Creates an SEO Project in the selected Account.”
Creates a new SEO project in the Lumar account you choose, with a name and the main domain of the site to crawl.
Run Crawl
ActionIn Zapier“Run a Crawl in the selected Project.”
Launches a crawl in an existing project of the Lumar account you choose, without anyone opening Lumar to start it.
When a Lumar Zap breaks
Zapier links no help article to Lumar and documents no limit specific to the app. The cases below come from the fields its operations require and from how Zapier itself behaves.
Six cases worth knowing before you publish, because none of them shows while you build. If one hits you, the Zapier troubleshooting page is a good place to start.
The crawl that never stops
Crawl Finished followed by Run Crawl on the same project writes where the trigger watches: every finished crawl starts a new one, and each one costs a task.The domain is refused
Create SEO Project expects the primary domain as an absolute URL. A bare domain name coming from another tool does not fit and the step fails.No project to pick
Run Crawl and Crawl Finished need an existing Project. If the project was never created, or your account has no access to it, the step cannot be set.Old crawls are not picked up
A Zap only reacts to what happens after you switch it on. Crawls and tasks that already existed stay out; moving that history is a separate job.A sudden flood of tasks
When a trigger suddenly returns a huge batch, after a bulk import for example, Zapier's flood protection can hold those items back instead of running them all.Duplicates are filtered out
On a polling trigger, Zapier keeps track of what it has already seen, so the same crawl or the same task never starts the Zap twice.
Need help automating Lumar with Zapier?
A person reads every message.
