Lofty Zapier integrationAutomate Lofty with Zapier.
The Lofty Zapier integration gives you 7 triggers, 5 actions and 1 search. Every trigger is instant, so a new lead or a transaction update reaches Zapier as soon as Lofty reports it, and the actions write leads and transactions back into your CRM.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lofty Zapier integration actually does
The Lofty Zapier integration connects Lofty, the CRM and tech suite real estate agents run their leads and deals in, to Zapier, a service that carries events from one app to another. It works both ways: Lofty can start an automation, and it can also receive leads and transaction changes from your other tools.
Three results show up again and again. A heads-up for every new lead: New Lead fires when a lead is assigned to you and posts it in the chat your team already watches, so nobody has to refresh the CRM. Documents that file themselves: Transaction File Uploaded passes each file added to a deal on to your file storage, where the rest of the paperwork lives. Leads from your website form, without retyping: Create Lead turns each form submission into a Lofty lead, with the option to send the welcome email at the same time.
What Zapier does not do for Lofty matters too. There is no delete action, so nothing removes a lead or a transaction from the CRM. The only search, Find Record, looks a record up by its Lofty ID and not by name or email. And Smart Plan Action only works for the accounts admitted to its beta.
If those limits weigh on your project, check the other platforms before building: the n8n vs Zapier and Make vs Zapier comparisons.
Zapier words in one minute
Eight words carry the rest of this page. Here they are in plain terms, once.
- 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. With Lofty it is a new lead, a lead moving segment or pipeline, or a transaction event.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, such as creating a lead in Lofty.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan counts those, and nothing else.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
- Search step
- A step that looks up something already in an app, so the steps after it can use what it found. Find Record is the Lofty one.
- Connection
- Your Lofty account linked to Zapier once, then reused by every step of every Zap that touches Lofty.
What a Lofty Zap really costs
The Lofty trigger never costs a task. Only the actions that run after it are counted, and only when they succeed.
- Lofty trigger0 tasks
- Each successful action1 task
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap size2 steps: one trigger, one action
- Premium appNo, Lofty works on the free plan
A Zap with three actions uses three times what a one-action Zap uses, and an action that fails is not counted. Lofty is not a premium app, so it works on the free plan, but that plan stops at two steps: one trigger, one action. Adding Find Record, a filter or a second action makes the Zap multi-step, which needs a paid plan. The grid below is how often Zapier checks polling triggers on each plan; it does not apply to the seven Lofty triggers, which are all instant.
Connect Lofty to Zapier in three steps
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. All you need at this point is a Lofty account you can sign in to with your usual login.
- 02
Pick Lofty
Type Lofty in the search box of the dialog, select it in the results, then click Add connection. A new tab opens on the Lofty side for the last step.
- 03
Sign in and grant access
Sign in to Lofty in that tab and grant Zapier access to the account. If the leads or transactions you want to touch belong to a colleague, your login needs read or write rights on them.
Your first Lofty Zap: new leads announced in your team chat
GoalEach lead newly assigned to you in Lofty posts a message in your team chat, as long as it passes the filter you set.
- 01
Create the Zap
Start a new Zap, pick Lofty as the app that starts it and New Lead as the event. Select the Lofty connection you added earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of your account, so map from a real lead rather than an empty sample.
- 03
Add the filter
Click the plus icon, choose Filter, then fill the three boxes: the field to look at, the rule, the value to compare with. Use a text rule for text and a number rule for numbers.
- 04
Add the chat message
Add the action of your chat tool and drop the lead's name and contact details into the message. Test the step and read what came back. To build the habit on your own Zaps, the Zapier training is the next stop.
- 05
Publish
Click Publish to switch the Zap on. The filter makes it a multi-step Zap, so it runs on a paid plan; drop the filter to keep it on the free plan.
The 7 Lofty triggers
7 events start a Zap when something happens in Lofty, and 7 of them are instant: the app calls Zapier straight away, whatever your plan.
Segment Changed
Instant triggerIn Zapier“Triggers when a lead is moved to the selected group.”
When a lead lands in the segment you picked, Lofty starts the Zap with that lead's details. Segments are how you sort leads in the CRM, so this trigger turns a sorting decision into an automatic next move.
Lead Pipeline Changed
Instant triggerIn Zapier“Triggers when a lead is moved to the selected pipeline.”
Moving a lead into the pipeline you selected sets off the Zap. It follows progress rather than arrivals: the lead already exists, it has just reached another stage of your process.
New Transaction
Instant triggerIn Zapier“New transaction trigger”
A transaction created in Lofty starts the Zap, carrying the new deal into the next step. It is the entry point for everything that should happen once a deal is opened.
New Lead
Instant triggerIn Zapier“Triggers when a new lead is assigned to you. Does not work for lender-type accounts.”
This one reacts when a new lead is assigned to you, not when any lead appears in the account. The lead's details then flow into whatever step comes next.
Smart Plan Action
Instant triggerIn Zapier“Trigger this zap when a specific Smart Plan step with a unique "Zap Trigger ID" is run for a lead.”
Inside a Lofty Smart Plan, a step can hand over to Zapier. When that particular step runs for a lead, this trigger starts your Zap, which lets a Smart Plan reach tools Lofty does not cover.
Transaction File Uploaded
Instant triggerIn Zapier“Fires when a new file is uploaded to a Transaction in Lofty.”
Adding a file to a transaction in Lofty sets the Zap off with that file. The document can then travel wherever the rest of your records sit.
Update Transaction
Instant triggerIn Zapier“Update transaction trigger”
An edit to an existing transaction starts the Zap, with the deal as it now stands. Pick it when what changes on a deal matters more than its creation.
The 5 Lofty actions
Lofty gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Lead
ActionIn Zapier“Creates a new lead.”
Adds a new lead to Lofty from what an earlier step carried, so contacts from forms or ads enter the CRM directly.
Create Transaction
ActionIn Zapier“Create Transaction Action”
Opens a transaction in Lofty, so a deal agreed elsewhere shows up in the CRM without retyping.
Update Lead
ActionIn Zapier“Updates an existing lead.”
Changes the details of a lead that already exists in Lofty, keeping the CRM in line with what your other tools learn.
Update Transaction
ActionIn Zapier“Update Transaction Action”
Edits an existing transaction, for example to move it to a new stage when something happens outside Lofty.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
An advanced step that sends your own request to Lofty, reusing the connection you already set up, for the cases the ready-made actions do not cover.
The Lofty search, and what happens when it finds nothing
1 search step looks for data that already exists in Lofty, so a later step can use it.
A search step sits at the bottom of the action list in the editor, under its own SEARCH heading. Three settings decide what the Zap does with its result.
Find Record
SearchIn Zapier“FindRecord”
Looks up one lead or one transaction in Lofty and hands it to the next steps, which is how Update Lead or Update Transaction knows what to edit.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps that needed it are skipped. Switch it on and the Zap carries on empty-handed.
- Create X if it doesn't exist yet?On apps that offer it, this box turns a search into find-or-create. Lofty has no find-or-create variant of Find Record, so a missing record stays missing.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Lofty Zap breaks
Zapier lists no limit of its own for Lofty. What goes wrong comes from how Zapier works, and four cases cover most of it.
Each case below is a rule of Zapier rather than a fault in Lofty. If a Zap still misbehaves after you checked them, the Zapier troubleshooting page is the next stop.
Old leads never come through
A Zap only reacts to what happens after you switch it on. Leads and transactions that already existed are not picked up; moving that backlog is a separate job.A Zap that keeps setting itself off
Update Transaction as a trigger and as an action in one Zap is the classic loop: each edit starts it again and the task count drains fast.A big import gets held back
When a trigger suddenly sends a huge batch, after a bulk import of leads or a migration, Zapier's flood protection can hold those items back.Find Record stops the Zap
If the ID you pass matches nothing, the search stops the Zap by default and the update after it never runs. Check the setting described above.
Need help automating Lofty with Zapier?
A person reads every message.



