Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Asked & Answered Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Can Zapier connect WhatsApp Business to a CRM using Webhooks by Zapier?

  • Nov 9, 2026 6:55 PM UTC
  • 2 replies
  • 15 views

I’m planning an automation for a real estate business using a new, dedicated phone number. The number is not registered yet, and I will not move or change our existing WhatsApp Business number.

The intended workflow is:
WhatsApp Business (Meta Cloud API) → Zapier → Webhooks by Zapier (POST) → Jetimob CRM.

Could you please clarify:

1. Can Zapier connect this new number directly to a WhatsApp Business Account (WABA), or is a Business Solution Provider (BSP) required? What setup steps or Meta requirements apply?
2. Does the “new incoming message” trigger provide the sender’s name, phone number, and message text?
3. Can Webhooks by Zapier send a POST request using multipart/form-data, with a custom Authorization-Key header, to a third-party CRM API?
4. Are there plan limitations for the WhatsApp trigger or Webhooks by Zapier?

Jetimob has confirmed that its lead endpoint accepts POST requests with multipart/form-data. I have not connected any account or shared API credentials.

2 replies

WebhookEngineer
Forum|alt.badge.img+1

An incoming WhatsApp message doesn’t always include the sender’s phone number, which matters for lead capture.

For 1, Meta documents a direct-developer Cloud API setup, so a BSP isn’t universally required. You’ll need a Meta app and WhatsApp account configuration for that setup, but this doesn’t establish that Zapier can register your new number. The Zapier connector’s onboarding requirements need to be checked separately.

For 2, Meta’s text-message example includes the profile name, sender number and text. That doesn’t guarantee those fields in every event or tell us how Zapier maps them into its output. Meta explicitly says phone-number fields can be omitted for users who adopt usernames, with a business-scoped user ID supplied instead:
https://developers.facebook.com/documentation/business-messaging/whatsapp/webhooks/overview

Check whether Jetimob requires a phone number. If it does, events without one need an exception path rather than automatic lead creation.

I couldn’t verify the current Zapier documentation for 3 and 4, so I wouldn’t confirm multipart/header configuration or plan eligibility yet.

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • Nov 9, 2026 8:43 PM UTC

Hi ​@Ribas Corretores de Imóveis 

Help link from Jetimob: https://www.jetimob.com/apps/zapier

How to integrate with Jetimob?

First, create your Zapier account and a new Zap. Then, configure the trigger, connect your Jetimob account using the access key, and set the actions that should be executed.

 

Help links for using the mentioned apps: 

 

TIP: When in doubt, test it out.

⚡ Troy Tessalone - AutomationAce.com | Top Zapier Solution Partner | #1 Zapier Community Contributor
Early access


Next Gen Zaps

Build and deploy automations from AI tools you already use. With Agentic Management, if anything breaks, the agent diagnoses the issue and proposes a fix.

Request access now


Terms & ConditionsAccessibility statement