Connect Facebook, Thumbtack, and HomeAdvisor Leads via Zapier -- ResponsePro

When to use this guide

This guide covers lead platforms that either lack a direct webhook you can paste, or send data in a format that needs a middle layer. Zapier receives the lead, maps the fields, and POSTs a clean JSON payload to your ResponsePro intake URL:

Your intake URL

https://intake.responsepro.app/your-client-id

Platform	Source value	Best path
Facebook / Instagram Lead Ads	facebook	Zapier native trigger (below)
Thumbtack	thumbtack	Zapier Catch Hook + Thumbtack webhook, or dedicated landing page
HomeAdvisor	homeadvisor	Zapier Catch Hook (similar to Angi direct webhook if HomeAdvisor offers CRM feed)
Angi	angi	Direct webhook preferred — Zapier only if needed
Google LSA	google_lsa	Separate guide — no Zapier trigger

The universal Zapier action (every platform)

Regardless of trigger, the ResponsePro action step is always the same:

Add action: Webhooks by Zapier → POST

URL: https://intake.responsepro.app/your-client-id

Payload type: JSON

Map at minimum phone. Add name, email, message, and a static source string for the platform.

Turn the Zap on and send a test lead. Confirm SMS arrives and the lead shows in your dashboard with the correct source tag.

Facebook / Instagram Lead Ads

Facebook Lead Ads has a native Zapier trigger — this is the most straightforward third-party integration.

Trigger: Facebook Lead Ads → New Lead. Connect your Facebook account and select the Page and lead form.

Action: Webhooks by Zapier → POST (see universal steps above).

Facebook Lead Ads payload

{
  "name":    "{{full_name}}",
  "phone":   "{{phone_number}}",
  "email":   "{{email}}",
  "message": "{{what_service_do_you_need}}",
  "source":  "facebook"
}

Replace {{field_name}} tokens with the actual field names from your Facebook lead form — Zapier shows them after you pull a test lead. The source value must be typed literally as facebook.

Lead Ads consent Facebook Lead Ads forms include their own consent language. Keep your form disclosures accurate and aligned with what you registered on your 10DLC campaign. ResponsePro still appends STOP/HELP to outbound texts.

Thumbtack

Thumbtack does not POST directly to arbitrary URLs on all account types. Two workable paths:

Path A: Thumbtack webhook → Zapier → ResponsePro

Create a Zap with trigger Webhooks by Zapier → Catch Hook. Copy the Catch Hook URL.

In Thumbtack pro settings, look for webhook or integration options (availability varies by market). If Thumbtack supports outbound webhooks, paste the Catch Hook URL. If not, use Path B.

After a test lead hits the Catch Hook, add the universal POST action to your intake URL with source: "thumbtack".

Path B: Dedicated landing page (no Thumbtack webhook)

Point your Thumbtack profile to a page on your website with a contact form that hardcodes source: "thumbtack". Full copy-paste form code is in the website webhook guide. This is often simpler than fighting platform webhook limits.

HomeAdvisor

HomeAdvisor (now part of the Angi network for many pros) can route leads via CRM webhook similar to Angi. If your account supports it, email crmintegrations@angi.com with your intake URL directly — see the Angi guide and use source: "homeadvisor" if you want them tagged separately from Angi-branded leads.

If HomeAdvisor only supports a Zapier Catch Hook, follow the same pattern as Angi Option 2 in the Angi guide, with this payload:

HomeAdvisor via Zapier

{
  "name":    "{{customer name fields}}",
  "phone":   "{{phone}}",
  "email":   "{{email}}",
  "message": "{{project description}}",
  "service": "{{service type}}",
  "source":  "homeadvisor"
}

One Zap per platform

Create a separate Zap (or separate webhook) for each lead source. That keeps the source field accurate and makes dashboard reporting meaningful. Do not send everything through one Zap with a dynamic source unless you are deliberately merging channels.

Full reporting walkthrough: multi-source lead tracking guide.

Test any Zap

Manual curl test (bypasses Zapier)

curl -X POST https://intake.responsepro.app/YOUR-CLIENT-ID \
  -H "Content-Type: application/json" \
  -d '{
    "name":    "Platform Test",
    "phone":   "5405551234",
    "message": "Testing facebook source",
    "source":  "facebook"
  }'

If curl works but Zapier does not, the issue is field mapping in Zapier — open the Zap history, inspect the POST step, and confirm phone is populated.

Need us to build the Zaps for you? Reply to your welcome email — included in onboarding.