- Home
- Resources
- Integrations
- LockedOn
LockedOn Zapier integrationAutomate LockedOn with Zapier.
LockedOn Zapier integration: 5 triggers and 4 actions, no search, to move clients, contacts, enquiries, inspections, offers and contracts between LockedOn and your other tools. What each one does, what it costs and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the LockedOn Zapier integration does for an agency
LockedOn is a CRM and marketing platform for real estate agents. Connected to Zapier, it announces five events the moment they happen (a new client, contact, enquiry or inspection, and a property status change) and accepts four kinds of records from other tools: enquiries, inspections, offers and contracts.
Three outcomes come up again and again. An enquiry nobody misses: New Enquiry fires as soon as one lands in LockedOn, and your messaging tool tells whoever is on duty. Enquiries that arrive elsewhere end up in the CRM anyway: a form on another site feeds Create Enquiry, with the person's name as the only mandatory value. And a cleaner listings follow-up: Property Status Change pushes each status move to a spreadsheet or a report, so the team reads it there without logging into LockedOn.
Now what Zapier does not do here. There is no search at all, so a Zap cannot look up an existing client or property before acting. Every action creates; nothing updates or deletes a record. No trigger watches offers or contracts, even though both can be created from Zapier. And Property Status Change is broader than its name: it also fires when a property is created or deleted, so many Zaps built on it need a filter.
Comparing tools before you commit? See n8n vs Zapier and Make vs Zapier.
Zapier vocabulary, in one minute
Seven words do most of the work on this page. Here they are, plainly, once.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that event happens.
- Trigger
- The event that starts a Zap, such as a new enquiry in LockedOn. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes something for you, like an inspection created in LockedOn.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan is a number of those per month.
- Polling vs instant
- Polling: Zapier asks the app for news on a timer. Instant: the app calls Zapier itself. All five LockedOn triggers are instant.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it there otherwise.
- Connection
- Your LockedOn account linked to Zapier once, then reused by every step of every Zap that touches LockedOn.
What it really costs
Short version: the LockedOn triggers cost nothing, each successful action costs one task, and LockedOn is not a premium app, so it runs on the free plan.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, 2-step Zaps
- Premium appNo
An action that fails is not counted, and watching for new events is free. The free plan gives 100 tasks a month and unlimited Zaps, limited to two steps each: one trigger, one action. A filter or a second action turns the Zap into a multi-step Zap, which needs a paid plan. The grid below shows how often Zapier checks a polling trigger on each plan. It does not apply to LockedOn, whose five triggers are all instant.
Connect your LockedOn account in 3 steps
- 01
Add LockedOn from the Apps page
In your Zapier account, open the Apps page and click + Add connection. Search for LockedOn in the dialog, select it, then confirm with Add connection.
- 02
Sign in to LockedOn
LockedOn opens in a new tab. Sign in with the account whose clients, enquiries and properties the Zaps will handle. For records that belong to a colleague, you need read or write access to them first.
- 03
Grant Zapier access
Approve the access Zapier requests. The connection appears on the Apps page, and every LockedOn step offers it in a dropdown, so one sign-in serves all your Zaps.
Your first Zap: alert the team when an enquiry comes in
GoalEach new enquiry in LockedOn goes through a filter that keeps only the ones meeting your condition, then your messaging tool posts an alert to the team.
- 01
Create the Zap
From your Zapier dashboard, create a new Zap. The editor opens on an empty trigger card: a Zap always begins with its trigger, never with an action.
- 02
Pick New Enquiry
Choose LockedOn as the app, New Enquiry as the event, then your LockedOn connection. The trigger is instant, so the editor shows a lightning bolt next to it.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent enquiries from your account. Pick one, so every field you map afterwards shows a real value instead of a blank.
- 04
Add the filter
Click the plus icon, add a Filter step and set its three boxes: the field, the rule, the value. A text rule only works on text and a number rule only on numbers.
- 05
Add the alert
Add your messaging tool as the last step and write the alert with the enquiry fields. Test it once and read what came back before going further.
- 06
Publish
Click Publish to switch the Zap on. The filter makes this a multi-step Zap, which needs a paid plan; without it, the Zap fits the free plan.
The 5 LockedOn triggers
5 events start a Zap when something happens in LockedOn, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.
New Client
Instant triggerIn Zapier“Triggers when a new client is created.”
Fires each time a client record is added in LockedOn. The Zap gets the new client straight away and can pass it to the next tool in your chain, a mailing list or a spreadsheet.
New Contact
Instant triggerIn Zapier“Triggers when a new contact is created.”
Clients and contacts each have their own trigger in LockedOn. This one reacts to every new contact record saved there, so it is the one to pick when the next tool should hear about contacts rather than clients.
New Enquiry
Instant triggerIn Zapier“Triggers when a new enquiry is created.”
Starts the Zap as soon as an enquiry is recorded in LockedOn. Because nothing waits for a check, it is the fastest way to put an enquiry in front of someone who can answer it.
New Inspection
Instant triggerIn Zapier“Triggers when a new inspection is created.”
Reacts when an inspection is booked in LockedOn. From there, the Zap can put it in a calendar, warn the person who will attend, or add it to a shared list of visits.
Property Status Change
Instant triggerIn Zapier“Triggers when a property status changes or a property is created/deleted.”
Follows the life of a listing. It fires when a property changes status, and also when a property is created or deleted, which makes it the broadest of the five triggers.
The 4 LockedOn actions
LockedOn gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Contract
ActionIn Zapier“Creates a Property Contract”
Adds a property contract in LockedOn, with the name of the person getting the contract as the required value.
Create Enquiry
ActionIn Zapier“Creates an Enquiry”
Records a new enquiry in LockedOn from another tool. The name of the person enquiring is the one value it insists on.
Create Inspection
ActionIn Zapier“Creates an Inspection”
Books an inspection in LockedOn, tied to the name of the person who enquired. That name is mandatory; the rest depends on what the source step carries.
Create Offer
ActionIn Zapier“Creates a Property Offer”
Logs an offer on a property. It is the only action with two mandatory values: the name of the person making the offer and the offer amount.
When it breaks
Zapier attaches no help article to LockedOn, and no limit specific to the app is documented. What breaks are the limits all Zaps share.
Each one has a symptom you can spot: a Zap that ran too little, or far too much. For anything these cards do not explain, the Zapier troubleshooting page goes further.
No catch-up on the past
A Zap only reacts to what happens after it is published. Enquiries or clients created before that are never sent, and moving the backlog is a separate job.A Zap that feeds itself
New Enquiry followed by Create Enquiry, or New Inspection followed by Create Inspection, writes into what the trigger watches: the Zap restarts and burns tasks fast.A big import held back
When a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back instead of firing them all.More events than expected
Property Status Change also fires on creation and deletion. Without a filter, a Zap meant for status moves runs on every new or removed listing too.
Need help automating LockedOn with Zapier?
A person reads every message.



