Zapier + Hatch: Integrate with Lead Sources

In this article, we’ll cover how you can connect via Zapier to bring in leads from various sources into Hatch.

We recommend giving Part One (Basics) and Part Two (Triggers and Actions) of our Zapier + Hatch series a read before proceeding!

Here’s How it Works

1. A potential customer fills out a lead form on your website, social media, or on a lead aggregator like StickyLeads. 
2. Once the form is submitted, a “Zap” will run and send that information over to Hatch.
3. Hatch receives that lead information and creates a Contact, which you can target for campaign by creating a workflow in Hatch. 

Creating the Zap

1. From the Zapier Dashboard, click Make a Zap. 
   
   
2. This will open the zap editor where you can create a series of steps from different triggers and actions. 
   
   
3. Set up your lead source as the trigger in your new Zap. This is the form or source you want coming into Hatch.  Search for the app you want to connect. For this example, we're going to connect our Facebook Ads account.
4. Once you find your lead source app, it will prompt you to select your Trigger Event. This is going to be different based on the app you are connecting but typically this is a variation of a new lead is submitted or a new entry is received (the language will change a bit depending on what App you are connecting).  For this example, we're selecting New Submission.  Select and click Continue. 
5. Next, you'll need to authenticate using your credentials or by logging into the app you are connecting. This will look a little different for each app depending on their policies. You may be asked to allow Zapier to access your app. Click Allow and Continue.
6. Once you've authenticated, you'll see the app is connected and you can Continue. 
7. At this point, most apps will prompt you to "test" the connection and pull up a test lead. This step is necessary in order to have data to use in the following configuration steps. The lead may or may not be a live lead from your account (it may just be test data that the app publisher chooses). Confirm that the test lead is showing the data needed for your zap, and then Continue. If not, you may need to select another test lead. 
8. Now it is time to select your Action. Upon selecting the Hatch app, choose the "Create Contact" action. Click Continue.
9. You will be asked to authorize a Hatch account. If you have previously authorized access to your Hatch org, you can select it from a drop-down. Otherwise, connect a new account. You may authorize connections to more than one Hatch org. 
   
   
10. After clicking Connect, you will receive a pop-up prompting you to enter the API key (this can be obtained from Hatch Support as covered in part 1).
    
    
    
11. After you have completed the authorization, you should see your Hatch account connected. It can be changed if the wrong account was selected. Click Continue.
    
    
    
    
12. Next, you will move onto Configuring your action. This involves selecting the form data sent to Hatch, mapping and/or naming the fields sent to Hatch, and choosing which workspace to send the data to. 
13. The action has some pre-set standard Hatch fields that we recommend mapping data into. Only 3 are technically listed as required by the action, however, it is important to note that Hatch requires contacts to have at least a phone number or email. You can hover over the field names to read a description of their meaning. A list of these is provided below in the FAQ as well. 
14. Click the + sign on a field name in order to map (insert) data from your form fields. This will pop-up a new screen where you can search for the available fields. These fields are generated by the test record generated from your trigger, so if you don't see a field you are looking for you may need to trigger a new test. 
    
    
    
    If you choose to enter text manually, this is considered "hard-coded": meaning that same exact value will appear on all Hatch contact records generated by the action. This is not typically recommended.
    
15. If you want to bring additional fields over that do not map to a Hatch standard field, you can map these to the Contact Details. Since details are custom, you will need to create a field name to appear in Hatch in addition to mapping the value from the form.  Click the "add value set" to add additional custom fields.
    
    In this example, I will create a contact detail to map my Facebook campaign name:
    
    
    
    
16. The Hatch standard field named "Source" will default to "Zapier", thus it is not required. However, we highly recommend creating a custom, meaningful value for this source field, since this will be the method by which we can target these leads in Hatch. In this example, I will name my source Facebook Leads but if you were creating a zap for your website you might name this Website Leads. Simply type in the value to "hard-code" it for all contacts generated by this zap. 
    
    
17. Finally, select a Board ID from the provided drop-down. If you do not see a Board ID you are looking for, you may not have authorized the correct Hatch Org.
    
    One Note: Hatch Contacts are actually associated to a back-end concept called a Hatch Department. The Board ID is what you a user sees in the UI. Board IDs are all associated to a Department. When you select a Board ID in the drop-down, the contacts will actually be available to all Boards associated to the same Department as the Board you selected.
    
    We understand this may be a confusing concept. All that to say-- if you have a single form that may need to send contacts to multiple Hatch boards, you may not need to create multiple zaps to achieve this. Please feel free to consult with your Hatch representative on the implementation as needed. 
18. Once everything has been mapped, hit Test and Review. If everything is working correctly, the Zap will create a test contact in your Hatch workspace. You will be presented with an Opportunity ID in the testing step "Data Out" if successful.
    
    
    
    
19. The final step is to confirm the test contact came through to Hatch with the expected format and details. Within Hatch, go to Contacts. Search for the name of the test contact that was sent.
20. If your Zap is ready to go live, the final step is to click Publish. 

Setting up a Hatch Speed to Lead campaign

If you would like contacts coming in through a Zapier connection to go directly into a Hatch campaign, the Zapier integration is only step 1--these additional steps will need to be completed in Hatch. 

• Create an audience that captures your Zapier contacts. Using our audience builder, your audience might look something like this (simply replace the highlighted value with the value of the source field you created in the zap):
  
  
  
  
• Create a campaign (we have a template library to get started or you can duplicate a campaign you use with other leads!)
• Create an instant launch workflow that will instantly drop new contacts from the audience into the campaign. 

FAQ

I'm having trouble mapping my form fields to the Hatch fields, the form data isn't what Hatch is expecting--what should I do?

If your form data is not exactly as expected for use with Hatch, there are a few routes you could take to solve this. Here's an example:

In my Facebook form, the lead name field is "Full Name". However, Hatch requires a "First Name" and "Last Name" fields. 

• Modify the form. Make sure to review if you have any other processes dependent on the form data first. 
• Use a Zapier formatter step between the Trigger and Action steps. This may require an upgraded account. 
• Accept some level of inaccuracy. In my example above, I have shown how to bypass the issue by mapping the entire Full Name to First Name, and adding a period to the required Last Name field. 

What are the expected fields on the Hatch contact?