- Home
- Resources
- Integrations
- Landstack
Landstack Zapier integrationAutomate Landstack with Zapier.
Landstack Zapier integration: 4 triggers, 0 actions, 0 searches. Four instant triggers tell Zapier the moment a My Site or a Letter is created, updated or deleted in Landstack, so your CRM, sheet or team chat stays in step with Landstack.
Verified Trustpilot reviews · AI, automation & growth agency
What the Landstack Zapier integration does
Landstack gives UK businesses detailed land data and insights for their development projects. The Zapier integration carries four of its events outside the app: changes to your My Site records and to your Letters. Each one reaches Zapier as it happens, and Zapier runs the steps you chose in your other tools.
A site pipeline everyone can read. New or Updated My Site adds or refreshes a row in a shared sheet, so the team sees every site without opening Landstack.
A letter log next to your deals. New or Updated Letter writes each Letter into your CRM or tracker, and nobody has to copy its details by hand.
A heads-up when something disappears. Deleted My Site and Deleted Letter post a message in your team chat, so a removal never goes unnoticed in the other tools.
What Zapier does not do here: Landstack exposes no action and no search on Zapier. A Zap cannot create a site, send a Letter or look up a record inside Landstack. Data flows one way, out of the app, and deletions are only reported, never undone.
Weighing the platform itself? See our Zapier review and our n8n vs Zapier comparison. Start with the trigger that matches your daily routine. On Zapier, Landstack offers four triggers, all instant, 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 Landstack, a site or a Letter that changes; 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.
- Instant trigger
- A trigger the app reports itself: it calls Zapier the moment the event happens. All four Landstack triggers work this way.
- 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 Landstack Zap costs in tasks
None of the four Landstack triggers ever costs a task. Waiting for changes is free too. 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: one Landstack trigger plus one action. A filter or a second action needs a paid plan. Landstack is not a premium app, so the free plan covers it. And since all four triggers are instant, the polling grid below never slows them down.
Connect your Landstack account
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. You need a Landstack account, plus access to the sites and Letters you want to follow if someone else owns them.
- 02
Pick Landstack
Type Landstack into the search box of the dialog, select it in the results, then click Add connection. A new browser tab opens on the Landstack side to sign you in.
- 03
Sign in and grant access
Log in to Landstack in that tab and allow Zapier to reach the account. The connection is stored once, and every Zap that uses Landstack picks it up without asking you to sign in again.
Your first Zap: saved site to sheet and team chat
GoalEach new or updated My Site lands in your sheet and pings your team chat.
- 01
Choose the trigger
Create a Zap, pick Landstack as the app that starts it and New or Updated My Site as the event. Then select the connection you made above.
- 02
Set the required option
Fill in Triggers when My Site is... with the change you care about. The Zap only listens for that event, so this choice decides what reaches your sheet.
- 03
Test it on real sites
Run the trigger test. Zapier brings back the three most recent items of the account, so the mapping is done on a real site. If none comes back, save or edit a site in Landstack first.
- 04
Add the sheet and the alert
Add your spreadsheet tool's action that creates a row and map the site fields into your columns. A second action posting in your team chat makes it a multi-step Zap, which needs a paid plan.
- 05
Test, then publish
Test each step once and read what came back. When the row and the message look right, click Publish. The lightning bolt in the editor confirms the trigger is instant.
The four Landstack Zapier integration triggers
4 events start a Zap when something happens in Landstack, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.
New or Updated My Site
Instant triggerIn Zapier“Triggers when a My Site is created and/or updated.”
My Site holds the sites you keep track of in Landstack. This trigger starts your Zap when one of them is added, changed, or both, depending on the option you set.
Deleted My Site
Instant triggerIn Zapier“Triggers when a My Site is deleted.”
The mirror of the previous trigger. When someone removes a site from My Site, Landstack reports it to Zapier and your Zap runs once for that deletion.
New or Updated Letter
Instant triggerIn Zapier“Triggers when a Letter is created and/or updated.”
Letters are the second record type Landstack shares with Zapier. Each time a Letter is created or edited, this trigger hands it over and starts your Zap.
Deleted Letter
Instant triggerIn Zapier“Triggers when a Letter is deleted.”
When a Letter is removed in Landstack, this trigger tells Zapier, and your Zap runs once for that removal. It closes the loop opened by the create-or-update trigger.
When a Landstack Zap breaks
Zapier links no help article to Landstack, and no limit specific to the app is documented. The cases below come from how Zapier works in general, plus the one required setting of the triggers.
None of these cases shows an error at setup. They appear later, as a missing site or a task count that climbs too fast. If one hits you, see our Zapier troubleshooting page.
Older sites and Letters never arrive
A Zap only reacts to what happens after it is switched on. Sites and Letters already stored in Landstack stay there, and moving them is a separate job.The required option is set wrong
Triggers when My Site is... decides which change starts the Zap. Pick the wrong one and the Zap keeps waiting while your sites change without it.A bulk change gets held back
When a huge batch of records changes 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 Landstack with Zapier?
A person reads every message.



