Submit a request

Articles in this section

See more

Zapier Integration

Avatar
ITS Helpdesk
Updated
Follow

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 Chime
  • 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 Chime to Zapier

First, navigate to the following link to find Chime'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 Chime:

mceclip1.png

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

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

zapier_integration.jpeg

 

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. 

If you are interested in a tool that might work for two-way syncing with Chime, please take a look at an alternative product, PieSync, which is also connected to Chime. See PieSync Integration for more information.

 

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

No, Chime'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 Chime within Zapier?

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

  • First Name
  • Last Name
  • Email
  • Phone
  • Lead Type
  • Source
  • Segment
  • Tag
  • Note
  • Subscription - Smart Plan (true/false)
  • Subscription - Property Alert (true/false)
  • Subscription - Market Report (true/false)
  • Min Price (Buyer)
  • Max Price (Buyer)
  • City (Buyer)
  • State (Buyer)
  • Zipcode (Buyer)
  • Street or Complete Address (Mailing Address)
  • City (Mailing Address)
  • State (Mailing Address)
  • Zip Code (Mailing Address)
  • Address (Buyer)
  • Min Beds (Buyer)
  • Min Baths (Buyer)
  • Beds (Seller)
  • Baths (Seller)
  • Price (Seller)
  • Address (Seller)
  • SqFt (Seller)
  • City (Seller)
  • State (Seller)
  • Zipcode (Seller)
  • Send Welcome Email (true/false)

*IMPORTANT:

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

 

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

When Chime 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
  • Lead Type
  • Source
  • Tag
  • Segment
  • Note
  • Agent Name
  • Agent Email
  • Agent Phone
  • Location (buyer)
  • Address (buyer)
  • City (buyer)
  • Zipcode (buyer)
  • State (buyer)
  • Street or Complete Address (Mailing Address)
  • City (Mailing Address)
  • State (Mailing Address)
  • Zip Code (Mailing Address)
  • Max Price (buyer)
  • Min Baths (buyer)
  • Min Beds (buyer)
  • Min Price (buyer)
  • City (seller)
  • Address (seller)
  • Zipcode (seller)
  • State (seller)
  • Baths (seller)
  • Beds (seller)
  • Price (seller)
  • Sq Ft (seller)
  • Subscription: Market Report (true/false)
  • Subscription: Property Alert (true/false)
  • Subscription: Smart Plans (true/false)

 

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

Zapier is integrated into each account separately and only initiates a Zap (see above for "triggers") if a lead comes in through that account. For example, if a lead 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 lead was then assigned to the Team Admin/Owner via lead 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. 

 

Can I update a pipeline stage in Chime using Zapier?

That specific action is not supported. However, as a workaround, you could have Zapier add a tag which could in turn trigger a Smart Plan that could have an action to change a lead's pipeline stage.

 

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

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 Chime as the trigger, check Zapier trigger settings to make sure that the lead in question actually fits into the trigger criteria (for example it's a new lead, the segment has changed, the pipeline 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 actually enabled. There should be a little switch next to it on your Zapier dashboard/zaps list that you can see it is enabled. If not, make sure to have it on.
  • The email address for the lead might already exist in Chime which means it can't duplicate.

 

The Zapier connection to Chime 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 lead sent to Zapier not having the right information. Zapier will capture the first lead in your Chime CRM after the initial set up, when using Chime as a trigger, to make sure it's working. However, it could be possible that the first lead 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 Chime you can leave the email field blank on a lead record. So, it is possible that the test lead 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 leads that you add might have the right information that you need thus avoiding this issue.
  2. Change the test lead until it shows "Test Successful." If there are other leads in your database that match the necessary fields, they might work correctly. You can continue sending test leads to get it to work in order to confirm the connection. You can find more information on how to work with test leads 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 Transaction Data?

Yes, the following transaction data may be synced:

Chime → Zapier Use Chime as a Trigger

Chime can synchronize the following fields to other third-party providers:

  • Basic Information

    • Transaction Name

    • Transaction Type
    • Transaction Stage
    • Associated Lead's Name
    • Associated Lead's Email
    • Associated Lead's Phone
    • Transaction Owner's ID
    • Transaction Owner's Name
    • Transaction Owner's Email
    • Close Price
    • Commission Rate
    • GCI
    • Team Revenue
    • Agent Revenue
  • Property Details
    • Property Address
    • Property Unit
    • Property Listing Status
    • Property MLS Listing ID
    • Property Label
    • Property List Price
    • Property Property Type
    • Property Bedrooms
    • Property Bathrooms
    • Property Square Feet
    • Property Lot Size (Sqft)
    • Property Note
  • Dates (Format: mm/dd/yyyy)
    • Close Date
    • Expected Close
    • Appointment Date
    • Agreement Signed Date
    • Offer Date
    • Contract Date
    • Appraisal Date
    • Home Inspection Date
    • Escrow Date
    • Expiration Date
  • Custom Fields

Zapier → Chime Use Chime as an Action

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

  • Transaction Name(Required)
  • Lead First Name(Required)
  • Lead Last Name
  • Associated Lead Email
  • Transaction Owner Email(Required)
  • Transaction Type(Required)
  • Transaction Stage
  • Close Price
  • GCI
  • Team Revenue
  • Agent Revenue
  • Timezone(Date will be converted to the set of time zone)
  • System Dates：
    • Closed Date
    • Expected Close
    • Appointment Date
    • Agreement Signed Date
    • Offer Date
    • Contract Date
    • Appraisal Date
    • Home Inspection Date
    • Escrow Date
    • Expiration Date
  • Custom Fields
  • Property
    • Property Address
    • Property Unit
    • Property Listing Status
    • Property MLS Listing ID  
    • Property Label
    • Property List Price
    • Property Type
    • Property Bedrooms
    • Property Bathrooms
    • Property Square Feet
    • Property Lot Size (Sqft)
    • Property Note

Logic

  • Parsing is supported for the following date format：

    • yyyy-mm-dd：2001-08-24

    • mm/dd/yy：08/24/01

    • mm-dd-yy：08-24-01

    • dd/mm/yyyy：24/08/2001

    • Apr 11, 2022

    • dd.mm.yyyy：24.08.2001

  • Sync Logic:
    • First, find whether the transaction owner's email is an existing team member
      • If not, the transaction sync will fail
      • If yes, then check to see if the same lead (by email) is assigned to the transaction owner.
        • If yes, then the transaction will be created for this lead, or if this transaction already exists on this lead, update the transaction.
        • If not, Chime will create the lead as a team lead, assign it to the transaction owner first, then create the transaction for the lead.

When the Trigger is Lead Pipeline Change, can it support pushing the Lead ID and Agent ID fields?

Yes.

  • When Trigger is "New/update Lead", add the "Agent ID" field,
  • When Trigger is "New/update Transaction", add "Transaction ID", "Associated Lead ID", "TransactionOwnerPhone" fields.
  • When the Action is "Create/Update Transaction, add "Lead ID", "Transaction ID", "Transaction Owner ID" fields, optional fields.
  • When the Action is "Update Lead", add the "LeadID" field, an optional field.

 

  • Supports finding transactions with agent id, lead id, and transaction id when using create/update transaction action:
    • First, find out whether the incoming transaction owner id or email value is a team member(Prioritize using transaction id to find)
      • If not found, import failed.
      • If found, within the scope of the Leads of the user as the primary agent, use the incoming Lead ID or Lead Email value to find if the Lead(Prioritize using lead id to find)
        • If the lead doesn't exist, create the lead and transaction for the user.
        • If the lead exists, then use the incoming transaction id or transaction name value to find the transaction in the lead. (Prioritize using transaction id to find)
          • If found, then update. (If find multiple transactions, all are updated)
          • If not found, then create the transaction for the lead. 
  • Support find a lead with lead id when using create lead/update lead action:
    • When the lead id and lead email have values at the same time, first use the lead id to find the lead accurately.

Is the "Find Record in Chime"an action that can be added?

Yes.

  • Add a new action, called "Find Record in Chime:
    • Object(Required): Chime's Object
      • Lead  
      • Transaction
    • Search Value (Required): Trigger's fields
    • Should this step be considered a “success” when nothing is found?
      • Yes
      • No
  • Instructions：

    • When Object selects Lead, search the Lead ID equal to the value of the "Search Value field" in Chime, and the search scope is the ID of the lead visible to the user account bound to Zap.

      • If it is found, all the information of the Lead will be returned, and the fields are same as the "New Lead" Trigger.

      • If note found, returns nothing.

    • When Object selects Transaction, search the Transaction ID equal to the value of the "Search Value field" in Chime, and the search scope is the ID of the visible Transaction ID to the user account bound to Zap.

      • If found, return all the information of the Transaction, and the fields are the same as the "New Transaction" Trigger

      • If not found, returns nothing.

    • For the last fields:

      • When True is selected, if the ID is found or not found in Chime, continue to the next step

      • When False is selected, if the ID is not found in Chime, the next steps will be skipped.

Questions?

If you have any questions regarding this topic or any others, please reach out to our Support Team via email at <support@chimeinc.com>, by phone at 1 (855) 981-7557, or by a chat with us through your Chime CRM. 

 

Related terms: Zapier, Integra zap, zap trigger

Related articles

Comments

0 comments

Article is closed for comments.

All Rights Reserved.

Contact Us: support@chimeinc.com | 8:00 AM - 8:00 PM EST, Mon - Sun