Zapier Integration — WhatsApp Profile API

Add a WhatsApp profile lookup step to any Zap. No custom app required — use the built-in Webhook by Zapier action. Five-minute setup.

Setup (5 minutes)

  1. Open a Zap → choose your trigger (form submit, CRM new contact, etc.).
  2. Add action → Webhooks by Zapier → GET.
  3. Configure the GET request:
    • URL: https://whatsapp-proxy.checkleaked.cc/number/{{number}} — URL: https://whatsapp-proxy.checkleaked.cc/number/{number} — map {number} to the trigger's phone field (digits only, no +).
    • Headers: x-rapidapi-key: YOUR_DIRECT_KEY
      • RapidAPI marketplace users: switch URL host to whatsapp-data1.p.rapidapi.com AND add header x-rapidapi-host: whatsapp-data1.p.rapidapi.com.
  4. Test the step → Zapier parses the JSON response, fields become mappable.
  5. Add a downstream action (update CRM, add Slack message, route to Sheets, etc.) and map fields like isWAContact, about, profilePic, isBusiness.

Common Zaps built on this

Form → WhatsApp lookup → CRM — when a new Typeform / Tally / Gravity Forms submission arrives, enrich the phone number and write a row in HubSpot / Pipedrive.
E-commerce → WhatsApp lookup → tag customer — on a new Shopify / WooCommerce order, validate the phone number and tag the customer as "on WhatsApp" or "business" for post-purchase automation.
Lead → WhatsApp lookup → Slack routing — incoming lead gets validated; if isBusiness: true, route to the sales Slack channel; if personal, route to self-serve nurture.
Sheet row → WhatsApp lookup → Sheet update — paste numbers into a Sheet column, a Zap validates each one and writes results back.

Rate-limit & quota notes for Zapier

Each Zap step counts as one API request. Zapier's task allowance is separate from your API quota — review both when planning volume. For large lists, use bulk validation instead of firing one Zap per row.

Troubleshooting

  • 401 Unauthorized: direct proxy needs only x-rapidapi-key with your direct-purchase key. RapidAPI marketplace also needs x-rapidapi-host: whatsapp-data1.p.rapidapi.com AND a key from your RapidAPI dashboard (a direct key won't work on RapidAPI base URL, vice versa).
  • Empty profilePic: the target user has set their profile picture visibility to nobody / my contacts. Not an error.
  • Zap runs but no response parses: re-run the test step — Zapier sometimes caches the first empty schema.

Related

What Our Users Say

Real reviews from our satisfied customers

4.5/5 (162 reviews)