Skip to main content

Zapier Integration

Updated

Introduction

Zapier is a powerful "middle-ware" tool that can be used to connect two services that are otherwise not connected. Zapier works as an app that can connect to a wide selection of products on the market. If you need Product A to connect to Product B, and Product A and B do not have a direct integration with each other, Zapier is a tool that can fit in the middle to facilitate the connection as long as both products can connect to Zapier. 

*IMPORTANT:

  • You will need a Zapier account to use this tool with LoftyWorks
  • Please note that many features on Zapier are free but there are paid plans that are available to increase the overall functionality and sync rate/frequency. Refer to Zapier's pricing pages for more information in this regard.

 

Summary

 

Connect LoftyWorks to Zapier

First, navigate to the following link to find LoftyWorks's integration on Zapier: Click Here.

Once there, make sure you are logged in and then search for the app that you would like to connect with LoftyWorks:

IZAP4.jpeg

Zapier will then walk you through the steps to connect the two services.

You will need to grab your LoftyWorks API key to connect LoftyWorks to Zapier. This is the unique identifier for your LoftyWorks account and is a requirement when connecting LoftyWorks to Zapier. To find your API key, navigate to Settings > Integrations > API > Copy:

 

Note: Company Owners or Admins can choose to synchronise all visible contacts and progressions to Zapier. 

 

FAQs

 

How does Zapier work?

Zapier can be as simple or as complicated as you would like it to be. You are best guided through how to use it by referencing Zapier's documentation. Please see Zapier: How It Works.

 

How do I learn more about definitions used within Zapier?

See Learn key concepts in Zapier for more information.

 

Does Zapier support two-way syncing?

No, two-way syncing is not supported via Zapier. For an explanation as to why, please see the following resource at Zapier: Click Here. If you aren't careful, you could accidentally create a "Zap loop" which could cause data issues, constant duplicate information being added to your system, etc. For more information on how to avoid that, Click Here. 

 

Can I use Zapier to perform any action I want within LoftyWorks?

No, LoftyWorks's Zapier integration is only as powerful as we have built it to be. In other words, we support certain actions and triggers. These are outlined below.

 

What are the "actions" that are supported for LoftyWorks within Zapier?

When LoftyWorks is used as the Action in a Zap, the following are the available options:

  • First Name
  • Last Name
  • Email
  • Phone
  • Contact Type
  • Source
  • Segment
  • Tag
  • Note
  • Subscription - Smart Plan (true/false)
  • Subscription - Property Alert (true/false)
  • Min Price (Buyer)
  • Max Price (Buyer)
  • City/Town (Buyer)
  • County (Buyer)
  • Postcode (Buyer)
  • Street or Complete Address (Mailing Address)
  • City/Town (Mailing Address)
  • County (Mailing Address)
  • Postcode (Mailing Address)
  • Address (Buyer)
  • Min Beds (Buyer)
  • Min Baths (Buyer)
  • Min Receptions (Buyer)
  • Beds (Seller)
  • Baths (Seller)
  • Receptions (Seller)
  • Price (Seller)
  • Address (Seller)
  • SqFt (Seller)
  • City/Town (Seller)
  • County (Seller)
  • Postcode (Seller)
  • Send Welcome Email (true/false)

*IMPORTANT:

  • In order for a "Segment", "Tag", or "Source" to be pushed into LoftyWorks via a zap, they must already exist in LoftyWorks and as a Segment, a Shared Tag, or a Source. The "Segment", "Shared Tag", or "Source" must be set up in LoftyWorks, or the Agent must have the required permission enabled, for any of these items to populate when the contact is created in LoftyWorks.
  • Currently, you can only send ONE "Segment" or "Tag" per Zap that is built. Adding in multiple is not supported at present. 

 

What are the "triggers" that are supported for LoftyWorks within Zapier?

When LoftyWorks is used as a Trigger, the following are the fields that can be pulled in and used in the corresponding Action: 

  • Email
  • First Name
  • Last Name
  • Phone
  • Contact Type
  • Source
  • Tag
  • Segment
  • Note
  • Agent Name
  • Agent Email
  • Agent Phone
  • Location (buyer)
  • Address (buyer)
  • City/Town (buyer)
  • Postcode (buyer)
  • County (buyer)
  • Street or Complete Address (Mailing Address)
  • City/Town (Mailing Address)
  • County (Mailing Address)
  • Postcode (Mailing Address)
  • Max Price (buyer)
  • Min Baths (buyer)
  • Min Receptions (Seller)
  • Min Beds (buyer)
  • Min Price (buyer)
  • City/Town (seller)
  • Address (seller)
  • Postcode (seller)
  • County (seller)
  • Baths (seller)
  • Receptions (seller)
  • Beds (seller)
  • Price (seller)
  • Sq Ft (seller)
  • Subscription: Property Alert (true/false)
  • Subscription: Smart Plans (true/false)

 

Is Zapier connected to individual user accounts or the entire team?

Zapier is integrated into each account separately and only initiates a Zap (see above for "triggers") if a contact comes in through that account. For example, if a contact comes in via a team member/agent's integration, it would not trigger the Zapier integration at the Team Admin/Owner's level. Also, in that same context, if that contact was then assigned to the Team Admin/Owner via contact routing, etc., it would still not trigger their Zapier integration. The only way to trigger Zapier for a team member/agent is if they have their own Zapier account integrated and zaps set up. 

 

What are some of the common reasons why my zaps are not working correctly with LoftyWorks? 

First of all, it's important to understand the basic flow of how Zapier works:

Trigger (App A, for example) --> Optional "Helpers" --> Action (App B, for example). 

If a problem occurs, it could happen at either of those three spots. Consider the following:

  • If you are using LoftyWorks as the trigger, check Zapier trigger settings to make sure that the contact in question actually fits into the trigger criteria (for example it's a new contact, the segment has changed).
  • One of the most common reasons why an action is not working correctly is because the "Helpers" could be getting in the way. These can consist of filters, etc. It would be good to check any "Helpers" that you have enabled in between the trigger and the action to see if the hold-up could be right there. 
  • Make sure the Zap is enabled. There should be a little switch next to it on your Zapier dashboard/zaps list that you can see is enabled. If not, make sure to have it on.
  • The email address for the contact might already exist in LoftyWorks which means it can't duplicate.

 

The Zapier connection to LoftyWorks has failed to confirm the connection, what can I do to fix it?

The most common reason for the connection failing to work is due to the test contact sent to Zapier not having the right information. Zapier will capture the first contact in your LoftyWorks CRM after the initial setup, when using LoftyWorks as a trigger, to make sure it's working. However, it could be possible that the first contact in your CRM does not match the conditions in action fields. For example, some apps need to use the "email" field, but, as you should know, in LoftyWorks you can leave the email field blank on a contact record. So, it is possible that the test contact might not have an email address thus resulting in a failed connection test. In other words, the connection is likely working but has failed due to the lack of an email address (in this example). 

Two solutions to consider:

  1. "Skip and Continue" if the Zap is already working correctly. Future contacts that you add might have the right information that you need thus avoiding this issue.
  2. Change the test contact until it shows "Test Successful". If other contacts in your database match the necessary fields, they might work correctly. You can continue sending test contacts to get it to work to confirm the connection. You can find more information on how to work with test contacts in the following Zapier article: Change the test data in your Zap trigger.

 

How can I best troubleshoot Zapier zaps?

Log into Zapier and click on Task History on the left menu. This will allow you to choose the zap that you want to check and review the history to determine where things might have gone wrong.

mceclip3.png

mceclip4.png

 

Can Zapier Sync Progression Data?

Yes, the following progression data may be synced:

LoftyWorks → Zapier Use LoftyWorks as a Trigger

LoftyWorks can synchronise the following fields to other third-party providers:

  • Basic Information
    • Sales Progression/Lettings Application
    • Progression/Application Stage
    • Associated Contact's Name
    • Associated Contact's Email
    • Associated Contact's Phone
    • Owner's Name
    • Owner's Email
    • Sales Price/Rent Amount
    • Commission Rate
    • Commission Revenue
    • Team Revenue
    • Agent Revenue
  • Property Details
    • Property Address
    • Property Unit
    • Property Status
    • Property Label
    • Property Asking Price
    • Property Type
    • Property Bedrooms
    • Property Bathrooms
    • Reception Rooms
    • Property Square Feet
    • Property Note
  • Dates (Format: dd/mm/yyyy)
    • Completion Date
    • Expected Completion Date
    • Appointment Date
    • Agreement Signed Date
    • Offer Date
    • Contract Date
    • Appraisal Date
    • Home Inspection Date
    • Expiration Date
  • Custom Fields

Zapier → LoftyWorks Use LoftyWorks as an Action

LoftyWorks will add a “Create Progression” Action to allow third-party providers to create and update the following Progression fields on LoftyWorks:

  • Progression Name(Required)
  • Contact First Name(Required)
  • Contact Last Name
  • Associated Contact Email
  • Owner Email(Required)
  • Sales Progression/ Lettings Application(Required)
  • Progression/Application Stage
  • Sales Price
  • Commission Revenue
  • Team Revenue
  • Agent Revenue
  • Timezone(Date will be converted to the set of time zone)
  • System Dates：

    • Offer Date

    • Offer Accepted Date

    • Memorandum of Sale Date

    • Application Submitted Date

    • Proposed Move-in Date

    • Survey Date

    • Holding Deposit Paid Date

    • Exchange of Contracts Date

    • Tenancy Start Date

    • Tenancy End Date

    • Mortgage Offer Date

    • Expected Exchange Date

    • Referencing Start Date

    • Referencing Completion Date

    • Right to Rent Check Date

    • Application Expiry Date

    • Expected Completion Date

  • Custom Fields
  • Property
    • Property Address
    • Property Unit
    • Property Status
    • Property Label
    • Property Asking Price
    • Property Type
    • Property Bedrooms
    • Property Bathrooms
    • Reception Rooms
    • Property Square Feet
    • Property Note

Logic

  • Parsing is supported for the following date format：
    • yyyy-mm-dd：2001-08-24
    • dd/mm/yy：24/08/01
    • dd-mm-yy：24-08-01
    • dd/mm/yyyy：24/08/2001
    • Apr 11, 2022
    • dd.mm.yyyy：24.08.2001
  • Sync Logic:
    • First, find whether the owner's email is an existing team member
      • If not, the transaction sync will fail
      • If yes, then the progression will be created for this contact, or if this progression already exists on this contact, update the progression.

 

Questions?

If you have any questions about this topic or anything else, please get in touch with our Support Team. You can email us at <Support@LoftyWorks.com> or call us on +44 330 321 3500.

Comments

0 comments

Please sign in to leave a comment.