Resources · Zapier integration

Loftyworks Zapier integrationAutomate Loftyworks with Zapier.

The Loftyworks Zapier integration gives you 5 triggers, 4 actions and 1 search. All five triggers are instant, so a lead assigned to you or a transaction edit reaches Zapier as soon as Loftyworks reports it, and the actions create or update leads and transactions.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Loftyworks Zapier integration actually does

The Loftyworks Zapier integration links Loftyworks, a CRM from Lofty Inc built for real estate agents, to Zapier, a service that carries events from one app to another. Traffic goes both ways: Loftyworks can start an automation, and it can also receive leads and transaction changes sent from your other tools.

Three results come up most. No new lead left waiting: New Lead posts a message in your team chat when a lead is assigned to you, so the first call happens while the contact is still warm. A deal tracker that stays current: Updated Transaction rewrites the matching row in your spreadsheet each time a transaction is edited. Form contacts straight into the CRM: Create Lead turns each entry of your website form into a Loftyworks lead, as long as the form collects an email and a first name.

What Zapier does not do for Loftyworks counts as much. No action deletes a lead or a transaction from Loftyworks. The only search, Find Record, works with a Loftyworks ID, never a name. And there is no advanced request step here, so the four actions are the whole write side of the integration.

If that is too narrow for your project, compare platforms before building: the n8n vs Zapier and Make vs Zapier comparisons.

Vocabulary

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 that starts the Zap. With Loftyworks it is a lead assigned or moved to a group, a Smart Plan step, 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 updating a lead.
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. Here, that is Find Record.
Connection
Your Loftyworks account linked to Zapier once, then reused by every step of every Zap that touches Loftyworks.
Cost

What a Loftyworks Zap really costs

The Loftyworks trigger never costs a task. Only the actions after it are counted, and only when they succeed.

  • Loftyworks trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks per month, unlimited Zaps
  • Free plan Zap size2 steps: one trigger, one action
  • Premium appNo, Loftyworks works on the free plan

A three-action Zap uses three times what a one-action Zap uses, and a failed action is not counted. Loftyworks is not a premium app, so it works on the free plan, but that plan builds two steps only: one trigger, one action. Find Record, a filter or a second action turn the Zap into a multi-step Zap, which needs a paid plan. The grid below shows how often Zapier checks polling triggers on each plan; it does not apply to the five Loftyworks triggers, which are all instant.

Connect

Connect Loftyworks to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. At this stage you only need a Loftyworks account you can sign in to with your usual login.

  2. 02

    Pick Loftyworks

    Type Loftyworks in the search box of the dialog, select it in the results, then click Add connection. A new tab opens on the Loftyworks side for the last step.

  3. 03

    Sign in and grant access

    Sign in to Loftyworks 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.

First Zap

Your first Loftyworks Zap: a group change feeds your mailing list

GoalWhen a lead moves into the group you picked in Loftyworks, it is added as a contact in your mailing tool, provided it passes your filter.

  1. 01

    Create the Zap

    Start a new Zap, pick Loftyworks as the app that starts it and Segment Changed as the event. Select your connection, then the group to watch.

  2. 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.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then fill the field, the rule and the value. A text rule works on text only, a number rule on numbers only.

  4. 04

    Add the mailing step

    Add the action of your mailing tool and map the lead's details into the contact fields. Test the step and read what came back. To build the habit on your own Zaps, the Zapier training is the next stop.

  5. 05

    Publish

    Click Publish to switch the Zap on. The filter makes it a multi-step Zap that runs on a paid plan; remove it to stay on the free plan.

Triggers

The 5 Loftyworks triggers

5 events start a Zap when something happens in Loftyworks, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Segment Changed

Instant trigger

In Zapier“Triggers when a lead is moved to the selected group.”

When a lead is moved into the group you selected, Loftyworks starts the Zap with that lead. Sorting a contact in the CRM becomes the cue for whatever should follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
add the lead to a matching list in your mailing tool as soon as it joins a nurture group.
Watch out
the group is a required setting, so it has to exist in Loftyworks before you build the Zap.
2

New Transaction

Instant trigger

In Zapier“Triggers when a new transaction is created.”

Every transaction created in Loftyworks sets off the Zap with the new deal. It is the starting point for anything that should happen once a deal opens.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
open a folder for the deal in your file storage, named after the transaction.
Watch out
if the same Zap opens transactions itself with Create Transaction, it writes where its own trigger watches and sets itself off in a loop.
3

New Lead

Instant trigger

In Zapier“Triggers when a new lead is assigned to you. Does not work for lender-type accounts.”

This trigger reacts when a new lead is assigned to you, not whenever a lead appears in the account. The lead's details then travel to the step you planned.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
post the lead's name in your team chat so the first call is never missed.
Watch out
Loftyworks states that it does not work for lender-type accounts.
4

New Smart Plan Action

Instant trigger

In Zapier“Triggers when a specific Smart Plan is executed for a lead.”

A Smart Plan is a sequence you run on leads inside Loftyworks. When a specific Smart Plan is executed for a lead, this trigger starts the Zap, so the sequence can reach tools outside the CRM.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
create a follow-up task in your task tool the moment a lead enters a given Smart Plan.
Watch out
it follows a specific Smart Plan, not every sequence; test it on a lead that really runs through that plan.
5

Updated Transaction

Instant trigger

In Zapier“Triggers when a transaction is updated.”

Any edit to an existing transaction starts the Zap, with the deal as it now stands. Choose it when the progress of a deal matters more than its opening.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
rewrite the deal's row in your tracking spreadsheet each time its stage changes.
Watch out
the Update Transaction action edits transactions too; inside the same Zap it sets this trigger off again and again.
Actions

The 4 Loftyworks actions

Loftyworks gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Lead

Action

In Zapier“Creates a new lead.”

Adds a new lead to Loftyworks from what an earlier step carried, so contacts gathered elsewhere land in the CRM.

When to use it
every entry of your website contact form should become a lead.
Watch out
email and first name are both required; a form that skips either one makes the step fail.
2

Create Transaction

Action

In Zapier“Creates a transaction record.”

Opens a transaction record in Loftyworks, so a deal logged in another tool appears in the CRM without retyping.

When to use it
a row marked as agreed in your spreadsheet should open the deal.
Watch out
four fields are required (transaction name, lead first name, type and stage), and earlier steps must supply all of them.
3

Update Lead

Action

In Zapier“Updates an existing lead.”

Changes a lead that already exists in Loftyworks, so the CRM keeps up with what your other tools learn about that contact.

When to use it
a contact sends corrected details through a form and Loftyworks should carry them.
Watch out
email is required; if that email already exists, the step succeeds without creating a duplicate lead.
4

Update Transaction

Action

In Zapier“Updates a transaction record.”

Edits an existing transaction record, for example to move it to the next stage when something happens outside Loftyworks.

When to use it
a deal closed in your spreadsheet should change stage in the CRM.
Watch out
it asks for the same four required fields as Create Transaction, stage included.
Searches

The Loftyworks search, and what happens when it finds nothing

1 search step looks for data that already exists in Loftyworks, 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 the result.

1

Find Record

Search

In Zapier“Finds a lead or transaction.”

Looks up one lead or one transaction in Loftyworks and passes it on, which gives the next steps the full record to work with.

When to use it
your spreadsheet keeps the Loftyworks ID of each deal and you need its current details.
Watch out
it searches IDs only, Lead ID or Transaction ID; a name will not match anything.

The three settings every search exposes

  1. 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. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    On apps that offer it, this box turns a search into find-or-create. Loftyworks has no find-or-create variant of Find Record, so a missing record stays missing.
  3. 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 it breaks

When a Loftyworks Zap breaks

Zapier lists no limit of its own for Loftyworks. 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 Loftyworks. If a Zap still misbehaves after you checked them, the Zapier troubleshooting page is the next stop.

  • Older leads never arrive

    A Zap only reacts to what happens after it is switched on. Leads and transactions that already existed are not picked up; moving them is a separate job.

  • A transaction Zap that loops

    Updated Transaction as the trigger and Update Transaction as the action in one Zap feed each other: every edit restarts the Zap and drains your tasks.

  • A bulk import gets held back

    When a trigger suddenly sends a huge batch, after a mass import of leads or a migration, Zapier's flood protection can hold those items back.

  • Find Record halts the Zap

    An ID that matches nothing stops the Zap by default, and the steps after the search never run. The setting explained above changes that.
Need help

Need help automating Loftyworks with Zapier?

A person reads every message.

FAQ

Loftyworks and Zapier: common questions

01Is the Loftyworks Zapier integration free?
Yes. Loftyworks is not a premium app, so it runs on the free plan, which gives you 100 tasks per month and unlimited Zaps. The catch is size: each free Zap has two steps, one trigger and one action. New Lead posting in your team chat fits. Add a filter to keep only some leads, Find Record before an update, or a second action such as a spreadsheet row, and the Zap becomes multi-step, which needs a paid plan.
02How many tasks does a Loftyworks Zap use?
The trigger costs nothing, however many leads or transactions come through. Each action that completes counts as one task, and a failed action is not counted. A Zap that adds every group change to your mailing tool costs one task per lead moved. Add a chat message on top and the same lead costs two. A few apps and actions take more than one task, so check the action you pick in your other tool too.
03Is the Loftyworks Zapier integration real time?
Yes, on all five triggers. Each one is instant: Loftyworks tells Zapier as soon as a lead is assigned or moved to a group, a Smart Plan runs, or a transaction is created or edited, and the Zap starts right away whatever your plan. The polling grid of the plans does not apply. A lightning bolt on the Zap in the editor confirms it, and there is no timing setting to change.
04What do you need to connect Loftyworks to Zapier?
A Loftyworks account you can sign in to, plus read or write access to any lead or transaction you do not own and want the Zap to touch. In Zapier, open the Apps page, click + Add connection, search for Loftyworks, click Add connection, sign in in the tab that opens and grant access. The connection is made once and reused by every Loftyworks step. Create the groups your triggers will watch before you build.
05Does Update Lead create a duplicate if the email already exists?
No. Update Lead requires an email address, and when that email already exists in Loftyworks, the step still succeeds without creating a duplicate lead. That makes the email the field to get right in the tool that starts the Zap: if it is missing, the required field stays empty and the step cannot run. Make sure every contact you send carries one. Create Lead needs the email as well, alongside a first name, so the same check covers both actions.
06What if the Loftyworks action you need is not in the list?
Then Zapier cannot do it for Loftyworks today. The four actions create and update leads and transactions; there is no delete action and no advanced request step to fill the gap. Check first whether Find Record plus an update covers your case. If not, the operation stays manual in Loftyworks, or you compare platforms to see whether one of them reaches it. Whatever you choose, keep the manual part documented so nobody expects the Zap to cover it.
07Zapier, Make or n8n for Loftyworks?
Choose on criteria, not on a ranking. Coverage first: on Zapier, Loftyworks offers 5 instant triggers, 4 actions and 1 search by ID, with no delete and no advanced request step, so compare those exact points. Cost next: Zapier bills each successful action and never the trigger, so multiply your leads and transactions by your actions. Upkeep last: count who on your team will maintain the flows over time. Weigh the three against your own flows.
Same platform

Other docs you might need on this stack.

Browse all integrations