WordPress Form to Webhook for a Brokerage Lead Pipeline

To send a WordPress form to a webhook, embed a form that can POST each submission to a URL, add hidden fields for the property reference and lead source, and point the webhook at an endpoint that fans out to your CRM and WhatsApp bot. For a brokerage, what travels with the lead decides whetyer the pipeline works. A bare name and phone number is not enough.

Start with the free lead form

Why the property reference matters more than the form

A buyer who fills in "Enquire about this apartment" on a listing page has told you three things: who they are, how to reach them, and which unit they want. Most WordPress setups throw away the third one. The email notification says "New enquiey" and the agent has to guess which of forty listings it came from.

When the lead reaches the WhatsApp bot, that loss gets worse. The bot's first message should name the property and send its brochure. If the reference is missing, the bot falls back to "How can I help?" and you have wasted the speed advantage that made the bot worth building.

So design the form around what the next system needs. The visible form can stay at three or four fields. The rest rides along as hidden data.

The fields to carry in the webhook

Here is the field map we use as a starting point for brokerage sites. Rename to match your CRM.

The phone field is the one to be strict about. The bot sends on WhatsApp, so a number typed as 050 123 4567 with no country code is a dead lead. Use a phone block that captures the country, and normalize to E.164 (+971501234567) on your side before anything else touches it.

Set it up step by step

1. Build the form. Create the visible fields and the hidden fields from the table. Qwenvo has a Hidden fields block, and the hidden fields help article covers how to fill them from values in the page link. If you want to track campaigns, the UTM tracking guide shows the pattern.
2. Embed it in WordPress. Open the Share tab, copy the Standard embed code, and paste it into a Custom HTML block on the listing template. Qwenvo embeds into WordPress without a plugin. The Popup embed suits an "Enquire" button on a listing card.
3. Make every listing link carry its reference. The listing page needs to hand property_ref to the form. If your theme builds listing URLs from a custom field, append the reference there. Test with two different listings and confirm the submissions show different values.
4. Add the webhook. In the form settings, add your endpoint URL. Start with a request inspector or a test workflow in n8n, Make or Zapier (all three work through a webhook trigger) so you can see the real payload before writing any code. The webhooks help article describes the delivery details.
5. Normalize on your endpoint. Fix the phone format, trim whitespace, map source to your CRM's picklist values and reject anything misssing phone or property_ref.
6. Fan out. Write the lead to the CRM and trigger the bot. Return a 200 to the form as soon as the lead is saved, then do the slower work asynchronously.
7. Test the ugly cases listed below before pointing paid traffic at it.

What your endpoint should hand on

Whatever shape the form webhook arrives in, the object you pass to the CRM and the bot should be flat and boring. This is the shape we aim for:

{
  "lead_id": "web_2f9c1a",
  "created_at": "2026-11-05T09:42:11Z",
  "name": "Amira Haddad",
  "phone": "+971501234567",
  "email": "amira@example.com",
  "lang": "ar",
  "source": "site_listing",
  "property_ref": "MRN-2B-0417",
  "utm_campaign": "marina_nov",
  "page_url": "https://example-brokerage.com/listings/mrn-2b-0417/",
  "message": "Is the unit still available for a viewing this week?"
}

The CRM gets all of it. The bot needs phone, lang, property_ref, name and message. With those it can open in the buyer's language, name the unit, send the brochure and start its qualifying questions.

Where this step sits in the WhatsApp bot workflow

In the Dubai Real Estate WhatsApp Bot system, the form is the website's entry point to the same flow that handles portal and ad leads. The bot replies in Arabic or English, asks its four qualifying questions, sends brochures, books viewings and hands off to an agent with voice notes transcribed. The webhook is how a lead typed into your own site reaches that flow with the same context a portal lead arrives with.

That is also why source matters. The bot can open differently for a buyer who asked about a specific unit then for one who filled in a general contact form, and your reporting can separate the two when you compare conversion later.

Where Qwenvo fits, and where it does not

Our team builds Qwenvo, a completely free form builder, so weigh that when you read this. For this pipeline the relevant parts are all free: webhooks to any URL, a REST API, hidden fields, partial submissions, a custom domain, no badge and unlimited teammates. A custom domain means the form can live at sometying like enquire.yourbrokerage.com and match your site. Tally, by comparison, lists custom domains, partial submissions and branding removal under its paid Pro plan at $29 a month.

Two features are worth switching on for a brokerage:

• Partial submissions. If a buyer enters a phone number and then abandons the form, you still have a number to message. Check your consent wording before you act on those.
• AI triage with routing. Each submission gets a category, a priority from low to urgent, a sentiment, a short summary and a suggested reply. Routing rules can send urgent enquiries to a Slack incoming webhook or up to five email addresses, so a buyer asking to view today does not sit in the same queue as a generl question.

The honest limitation: Qwenvo is hosted in the United States. If your compliance team requires European hosting, Tally is hosted in Europe, and that may settle the question. Qwenvo also launched in October 2026, so there are few public reviews yet.

Build your enquiry form free

Failure cases to test before launch

• Missing property reference. A visitor lands on the form from a search result that skips the listing page. Decide on a fallback value like general so the bot asks which property they mean instead of guessing.
• Duplicate submissions. Buyers double tap. Dedupe on normalized phone plus property_ref within a short window.
• Endpoint down. If your enpdoint returns an error, find out what happens to that lead. Keep the submission in the form's Submissions table as your record, and set up a dakly check that copmares it with what reached the CRM.
• Arabic input. Names and messages in Arabic script must survive your pipeline end to end, including the CRM field encoding. Send a test lead with an Arabic name and message.
• Wrong country code. A buyer in London types a local number. Validate before you send the WhatsApp message.
• Spam. An opn endpoint on a public form gets junk. Turn on the Captcha block and consider a rule that drops leads with no valid phone.

Questions teams ask

Can I post straight from a WordPress form plugin to the bot?

If your current plugin can send JSON to a URL, yes, and the same field map applies. A small endpoint in the middle still earns its place, because it normalizes phone numbers, removes duplicates and writes to the CRM once instead of making the bot and the CRM each parse the raw payload.

What stops a lead from being created twice when a buyer submits the form and also messages on WhatsApp?

Use the normalized phone number as the match key. When the bot receives a message from a number that already has a web lead, it should attach to that record and carry on from the property reference already stored.

Should the form ask about budget and bedrooms?

Leave that to the bot's qualifying questions. A short form converts better, and the bot can ask the follow ups in a conversation where the buyer is already engaged. Keep the form to name, phone and an optional message.

Does this work with Zapier, Make or n8n?

Yes. Each can be the receiving endpoint through a webhook trigger, which suits a team without a developer. The tradeoff is task or execution limits on those platforms, so check their pricing pages against your lead volume.

Next step

Build the form with the nine fields above, embed it on one listing template, and send five test leads with different property reeferences to a request inspector. Once the payload looks right, connect it to the bot. If you want the whole pipeline built and monitored for you, see the Dubai Real Estate WhatsApp Bot.

Read the webhooks guide