- Home
- Resources
- Integrations
- LandTech
LandTech Zapier integrationAutomate LandTech with Zapier.
LandTech Zapier integration: 2 triggers, 0 actions, 0 searches. Two triggers let Zapier pick up each new site and each title document you buy in LandTech, then pass them to your CRM, sheet or team chat on a schedule set by your Zapier plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the LandTech Zapier integration does
LandTech helps property professionals source, fund and move their projects forward faster. The Zapier integration brings two of its events into your other tools: a site that has just been created, and a title document that has just been purchased. Zapier checks LandTech for both, then runs the steps you chose.
A deal pipeline that starts itself. New Site creates a deal in your CRM for each site created in LandTech, so the follow-up begins without anyone retyping it.
A title document log. New Title Document adds a row to a shared sheet every time one is bought, so you can see at a glance which titles are already bought.
A heads-up in your team chat. Either trigger can post a message there once Zapier picks up a new site or document on its next check.
What Zapier does not do here: LandTech exposes no action and no search on Zapier. A Zap cannot create a site, order a title document or look anything up inside LandTech. Data flows one way, out of the app. Both triggers also work by polling, so nothing arrives the very second it happens.
Weighing the platform itself? See our Zapier review and our Make vs Zapier comparison. Start with the trigger closest to your daily work. On Zapier, LandTech offers two triggers, both checked on a timer, and no action.
Zapier vocabulary in one minute
Eight words carry this page. Here is each one in plain terms.
- Zap
- The automation you build on 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. With LandTech, a new site or a new title document; once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, here always in another app.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and the number on your plan counts those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen. Both LandTech triggers work this way.
- Instant trigger
- A trigger the app reports itself, calling Zapier the moment the event happens. LandTech offers none on Zapier.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it right there otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
What a LandTech Zap costs, and how often it checks
Neither LandTech trigger costs a task, however often Zapier checks. You only pay for the actions that follow, one task per action that succeeds.
- Trigger cost0 tasks
- Free plan100 tasks a month
- Steps per Zap on Free2 (trigger + 1 action)
- Premium appNo
A failed action is not counted. A Zap with three actions uses three times more tasks than a Zap with one. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, and polling runs every 15 minutes. A filter or a second action needs a paid plan. LandTech is not a premium app, so the free plan covers it. Here the grid below matters: it sets how long a new site waits before your Zap sees it.
Connect your LandTech account
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. You need a LandTech account, plus access to the sites and documents you want to follow if someone else owns them.
- 02
Pick LandTech
Type LandTech into the search box of the dialog, select it in the results, then click Add connection. A new browser tab opens on the LandTech side to sign you in.
- 03
Sign in and grant access
Log in to LandTech in that tab and allow Zapier to reach the account. The connection is stored once, and every Zap that uses LandTech picks it up without asking you to sign in again.
Your first Zap: new site to CRM and team chat
GoalEach site created in LandTech becomes a CRM deal and pings your team chat.
- 01
Choose the trigger
Create a Zap, pick LandTech as the app that starts it and New Site as the event. Then select the connection you made in the previous section.
- 02
Test it on real sites
Run the trigger test. Zapier brings back the three most recent sites of the account, so the mapping is done on a real one. If none comes back, create a site in LandTech first.
- 03
Add the CRM deal
Add your CRM's action that creates a deal, then map the site's fields into it. Every deal created successfully counts as one task, whatever the polling interval.
- 04
Add the team alert
Add a second action that posts in your team chat. That makes it a multi-step Zap, which needs a paid plan; on the free plan, pick either the deal or the alert, not both.
- 05
Test, then publish
Test each step once and read what came back. When the deal and the message look right, click Publish. From then on, Zapier checks LandTech at your plan's interval.
The two LandTech Zapier integration triggers
2 events start a Zap when something happens in LandTech. Zapier checks for them at the interval your plan allows.
New Site
Polling triggerIn Zapier“Triggers when a site is created.”
Each site created in LandTech is picked up by Zapier on its next check and starts your Zap once. This is the way to follow your sites outside LandTech.
New Title Document
Polling triggerIn Zapier“Triggers when a new title document is purchased.”
When someone on the account purchases a title document in LandTech, this trigger brings it to Zapier on the next check. It follows the purchase, not the site itself.
When a LandTech Zap breaks
Zapier links no help article to LandTech, and no limit specific to the app is documented. What breaks is Zapier's general behavior, and each case can be planned for.
None of these cases shows an error at setup. They appear later, as a missing site, a delay you did not expect or a task count that climbs too fast. If one hits you, see our Zapier troubleshooting page.
Older sites never arrive
A Zap only reacts to what appears after it is switched on. Sites and title documents already in LandTech stay there, and moving them is a separate job.The new site shows up later than expected
Both triggers poll. On the free plan Zapier checks every 15 minutes, so a site can wait that long. Paid plans check more often and allow a manual check.A bulk import gets held back
When a huge batch of sites appears at once, after an import or a migration, Zapier's flood protection can hold it back instead of running every item.The extra step stays locked on Free
A filter or a second action turns the Zap into a multi-step Zap. The free plan stops at two steps, so that Zap needs a paid plan.
Need help automating LandTech with Zapier?
A person reads every message.



