Watch this video tutorial on how to export data from Homebot using Zapier or follow the written instructions below.
Pulling data from Homebot (Using a webhook as the trigger)
Select the “Zaps” under the orange “+ Create” button - this will take you to the setup screen
Click “1. Select the event that starts your Zap,” also known as the Trigger, and select “Webhooks by Zapier”
Next you’ll select “Catch Hook” as your “Trigger Event” and then click “Continue”
NOTE: It’s important to select “Catch Hook” and NOT “Catch Raw Hook” for this step
Enter “Attributes Event Data” in the “Pick off a Child Key” field of the Configure step, then select “Continue”
The “Your Webhook URL” is the URL that Zapier has generated to receive requests. You’ll copy that URL to save for the next “Action” step set up
Skip the “Test Trigger” step for now and move on to the Action set up and search for and select “Homebot”
Select “Create Webhook Client” as the “Action event”
Next, you’ll connect your Homebot account and select “Continue”
Next, you’ll set up your configuration:
Name - This is the name of the webhook and can be any name of your choice. It’s used to differentiate between multiple webhooks. We recommend something simple like “Zapier Homebot Events Webhook”
Webhook URL - this is the Zapier-generated URL that you created and copied as part of step 5 (if you forgot to copy it you can always navigate back into the “Test” step of the “Catch Hook” Trigger step and re-copy it at this point)
Event Sources Whitelist - We group our client events into different sources eg. all events that are related to a client’s actions in the home digest are grouped under the “home-digest” event source
If you know you only want to receive events from a certain source eg. the home digest vs. the buyer digest you can select that source as part of this step to filter out other event sources
If left blank, you’ll receive all events from all sources
Username - Leave blank
Password - Leave blank
Click “Continue”
Next you’ll select “Test Step” - this action is creating the Webhook Client, successfully completing the “Test Step” is the only action you will need to take in order to create the Webhook Client
You should see a success message of “A Webhook Client was sent to Homebot (1.4.0) about 0 seconds ago” Woohoo! You’ve created your Webhook Client! 🎉
You DO NOT need to select “Publish”
Now that you’ve created your Webhook Client you can delete the “Create Webhook Client” Action step
The next step will be to create a sample trigger for the webhook to catch. This involves logging into your Homebot account and either setting up a test client with your email or using your own client profile if you’ve added yourself as a client in Homebot to create that sample trigger
You’ll navigate to that client profile and select “Send Home Report”
Open your email and click into the digest link that was just sent to you
Next you’ll take an action within that home digest that you want Zapier to be able to track for you eg. requesting a CMA, tuning the home value, sending a DM, etc.
Once you’ve completed that test action you’ll navigate back to Zapier
Next, you’ll test your “Catch Hook” Trigger step
After a successful test of the trigger select the corresponding request that matches the type of event you triggered in Homebot and click “Continue with selected record” eg. if you tuned the home value you should see a “client-tuned-value” action
Next, you’ll add a new Action step to retrieve the client information that was caught by the webhook. Search for and select the Homebot Zapier app
Select “Find Client by ID” as the “Action Event"
Select your Homebot account in the “Account” field and click “Continue”
For the “Client ID” field select “Attributes Event Data Client ID”
Leave “Should this step be considered a success if no search results are found?” set to “No” and leave the “Create Homebot Client if it doesn’t exist yet?” checkbox unchecked
Click “Continue”
Select “Test step” to test the action, you should see a success message of “A Client was sent to Homebot about 0 seconds ago”
Next, select the plus sign below the “Find Client by ID” action to add another action step
You’ll search for and select your desired destination for Homebot-generated client events. In our example we’ll be using Google sheets, but you can select your CRM or any other system’s you’d like as the destination for this data
Next, you’ll select the “Action Event“ that you want to happen when you receive a new Homebot client event
In our Google Sheets example this will be “Create Spreadsheet Row,” but if you’re using your CRM it might be the creation of a note in that client’s profile or the creation of an insight that you can that allows you to trigger a marketing campaign or journey within your CRM for that client
Select your “Account” in the right-side panel, in our example this would be the Google Sheets account containing the spreadsheet you wish you push Homebot client event data to
If you’re pushing client event data to your CRM the account will be your CRM account or your account with whatever platform you wish to connect to Homebot
Click “Continue”
Next, you’ll configure your CRM’s Action step:
In our example we’re selecting the Google Drive location of our spreadsheet. Choose between “My Drive” or a “Shared Drive”; the former is the default
Select the name of the Google Spreadsheet you wish to import Homebot client event data to in the “Spreadsheet” field
The “Worksheet” will be the specific sheet/tab of that spreadsheet you’d like to import the data to (eg. Sheet1)
You’ll then complete the rest of your configuration by selecting the client data that you wish to receive in addition to the client event webhook eg. what other information about that client will be helpful to know in addition to the behavioral signal. In our Google Sheets example these fields come from the headers of the sheet we created, but these could be the relevant fields within your CRM
Here’s a sample client data configuration:
The “Datetime” field of our Google sheet will map to “Attributes Create At” under Catch Hook to receive the time that a given client event was created
The “Source” field of our Google Sheet will map to “Attributes Event Data Source” under Catch Hook to receive the source of a given client event eg. home digest, buyer digest, etc.
The “Event Type” field of our Google Sheet will map to “Attributes Event Data Action” under Catch Hook to receive the type of client event triggered eg. client tuned value, viewed their digest, requested a CMA, etc.
The “Client First Name”/”Client Last Name” fields of our Google Sheet will map to “Data Attributes First Name”/”Data Attributes Last Name” respectively under Find Client by ID to receive the client’s first and last names
The “Client Email” field of our Google Sheet will map to “Data Attributes Email” to receive the client’s email address
Click “Continue” once configuration has been completed
Select “Test Step”, you should see a success message of “A Spreadsheet Row was sent to Google Sheets (or your CRM) about 0 seconds ago”
Navigate to the platform that the data was sent to to confirm it was successfully received. In our example this would be seeing that data populate in the Google Sheet
Select “Publish”
Your Zap is now fully operational and will automatically push your configured Homebot client events into your desired platform! 🥳
Additional Filtering
If you know you’d only like to receive a certain subset of our client events we highly recommend adding an optional, additional filter step to your Zapier workflow:
Select the “Edit Zap” button
Select the plus sign between the “Catch Hook” trigger step and the “Find Client by ID” action step to add a step. Search for and select “Filter by Zapier”
Under “Only continue if” you’ll select “Attributes Event Data Action” for the “Choose field” section
For “Choose condition” you’ll select how specific you’d like your filter to be. For our example we’ll select “(Text) Exactly matches”
For “Enter text or insert data…” you’ll enter the name of the specific event you’d like to receive. For our example we’ll enter “client-tuned-value”. Other examples of client event names you might want to receive could include:
client-tuned-value
cma-request
homeowner-direct-message
buyer-direct-message
Click “Continue”, and finish by testing your filter. You should see a success message of “Your Zap would have continued for this test data” with a green check
Your filter set up is complete! 🥳