The Angi Ads API can send to one endpoint URL only. This means that if you need to send new leads from Angi Ads to your CRM system + Hatch, you will need to use Zapier. The steps below walk you through this process.
Navigate to this article first to set up a webhook with Zapier and complete the integration on Angi Ads. Once you've reached Step 11, you will choose Hatch as the CRM under Action, and then return to this article for further instructions.
Once you see the information for the new lead from Test User in Indianapolis, IN, click Continue with selected record.
In the second step for Hatch, verify that *Event is set to "Create Contact", then click Continue.
Under the Account tab, click on Choose where it says "Choose an Account".
Click +Connect a New Account.
In the box that says "Allow Zapier to access your Hatch Account?", you will paste the LEGACY API KEY that Hatch provided you and then click Yes, Continue to Hatch. *Note: You must have a Legacy API Key, not a normal one.
Click the Action tab, and then click for each of the preset options for first name, last name, phone and email. Select the appropriate fields for each. See example.
Next, you will click the plus (+) sign at the bottom right of the Contact Details box to add the fields that Hatch uses for Angi Ads Integration, as shown in the image below.
Under the section asking for any additional fields, you will choose your Board ID (typically your Speed to Lead campaign), and type Angi Ads in the Source box. Then click Continue.
Go back to the top of the box and select the Test tab, then the blue Publish button to activate your integration.
Your integration is now live! You will still be notified of all new leads from Angi Ads just as you have been up to this point. They will also still be available in your Angi for Pros desktop site and Angi Ads Pro App, should you need to access them within the Angi Ads platform.
Please Note: While these steps are meant to assist you, if you need further support, please contact your Hatch representative or support@usehatchapp.com, as we do not have the ability to troubleshoot Hatch or Zapier on our end.