Skip to main content
Question

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

  • Nov 9, 2026 6:55 PM UTC
  • 4 replies
  • 52 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.

4 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
  • 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.


Before connecting the live number, I would verify the connector’s onboarding and plan requirements with the providers, then test each boundary separately. Send a test message to the dedicated number and inspect the actual trigger fields; include a case with no phone number and route it to review if the CRM requires one. For the CRM step, use test records and confirm the exact field names, response and authentication method with its team. Never share the key or real customer payloads in the forum. Test duplicate deliveries and a failed or timed-out POST before enabling the workflow; reconcile uncertain outcomes rather than blindly creating the same lead twice.

 

Drafted with AI help, reviewed by me.


Huzaifa_ZP
  • Beginner
  • Nov 13, 2026 11:20 AM UTC

I set this exact chain up earlier this year (Cloud API number straight into a CRM over a raw POST), so here is what I hit on each of your four points.

1. No BSP required, but Zapier will not register the number for you.

Zapier’s WhatsApp Business connector authenticates directly into Meta, so you do not need a Business Solution Provider in the middle. What it will not do is provision the number. All of that happens in Meta Business Manager before you open the Zap editor:

  • Add the new number to your existing WABA and verify it. A second number on the same WABA is fine, you do not have to touch your current one.
  • Get a display name approved. Unapproved display names fail with Meta error #131037 and Zapier cannot resolve that on your behalf.
  • Make sure the number is not signed in to the consumer WhatsApp app or the WhatsApp Business phone app. If it is, delete that account from the phone first or registration in WhatsApp Manager will fail.

Then in Zapier it is Apps, Add connection, WhatsApp Business, Connect WhatsApp Business Account, and pick the business profile plus the number.

2. Yes to all three fields, but you will not see them while testing.

New Message Received is an instant trigger and it carries the sender WhatsApp ID (phone in international format), the profile name Meta passes along, and the message text.

The part that cost me time: the test step returns a static placeholder sample, because the Cloud API has no endpoint for message history. Real values only appear after the Zap is on. So publish the Zap first, message the number from your own phone, then open Zap History and build your Jetimob field mapping from that live run instead of from the test record.

On the point raised above about missing phone numbers, I agree. Treat profile name as optional and do not assume every event is a plain text message. I put a Filter directly after the trigger that continues only when both the message text and the sender ID exist. Everything else goes to a Google Sheet for manual review rather than becoming a CRM lead.

3. Custom header yes, multipart is not a dropdown option.

The Headers section on the Webhooks by Zapier POST action accepts any header name, so Authorization-Key on the left and your key on the right works. Put it there, not in the Data section.

Payload Type only offers Form (url encoded), JSON, XML and Raw. There is no multipart/form-data choice. In my testing the request only goes out as multipart when the POST actually carries a file object in a data field, so a text only lead payload will leave as url encoded.

Two things I would do before building around that:

  • Ask Jetimob whether the lead endpoint also accepts application/x-www-form-urlencoded. Plenty of endpoints that document multipart read both, and if theirs does, the plain Form payload type is all you need.
  • Point the Zap at a request inspector such as webhook.site for one run and read the Content-Type you actually produced. Two minutes, and it settles the question with evidence instead of guesswork.

If they truly require multipart, add a Code by Zapier (JavaScript) step and build the body yourself:

const form = new FormData();form.append('name', inputData.name);form.append('phone', inputData.phone);form.append('message', inputData.text);const res = await fetch('https://your-jetimob-endpoint', {  method: 'POST',  headers: { 'Authorization-Key': inputData.key },  body: form});return { status: res.status, body: await res.text() };

Do not set Content-Type manually there, fetch adds the multipart boundary for you. Map name, phone, text and the key in as input data so the key never sits hardcoded in the code box.

4. Plan limits: both apps are premium.

WhatsApp Business and Webhooks by Zapier are both premium apps, so this workflow needs a paid Zapier plan. Worth flagging that the WhatsApp Business help article shows Free in its plans badge and then states under Prerequisites that a paid account is required because it is a premium app. The prerequisites line is the one that matched what I saw.

Other ceilings to keep in mind: webhook action payloads cap at 5MB, Webhooks by Zapier has its own rate limits, and Zapier static IPs for allowlisting are a Professional and up feature, which matters if Jetimob ever asks you to allowlist a source IP.

One last trap. WhatsApp Zap runs are reported as successful even when Meta failed to deliver the message. If you later add an auto reply back to the lead, do not trust the green status in Zap History. Check the conversation in Meta Business Manager, or run a second Zap on the Message Status Updated trigger and log sent, delivered, read and failed to a sheet.

Sources if you want to check me:
https://help.zapier.com/hc/en-us/articles/40123068069005-How-to-get-started-with-WhatsApp-Business-on-Zapier
https://help.zapier.com/hc/en-us/articles/8496326446989-Send-webhooks-in-Zap-workflows