Connect any platform,
capture every lead.
Not every site you own runs on WordPress. Web Hooks let a separate marketing site, landing page, or custom-built front end send its contact forms straight into your CRM — signed on the way in, deduplicated against your existing contacts, and attributed to the right source and agent.
Web Hooks — what it does
Inbound Endpoints
Give any external platform a URL to post leads to, and they flow straight into your CRM.
Standard Fields
Name, email, phone, message, source, type, and budget are accepted out of the box.
Signed Requests
Every endpoint issues its own signing key. Submissions are verified before anything is stored, so they cannot be altered in transit or replayed.
Delivery Log
Every call is logged with timestamp, endpoint, status, and the lead it created.
Configurable
Name each endpoint, set its source label, default agent and lead type, issue a new signing key, or switch it off without deleting it.
Simple Admin UI
Manage everything from Overview, Endpoints, and Logs tabs in WP Admin.
Three places leads go missing
Every one of these ends with a contact in GenieCRM™, attributed to where it came from.
Facebook & Instagram lead ads
Someone fills in a lead form without ever leaving Facebook. Instead of that name sitting in Ads Manager until somebody exports a spreadsheet, it arrives in the CRM within seconds — assigned, notified and followed up while the ad is still in front of them.
A landing page on another domain
A campaign page built in Unbounce, Webflow, Squarespace or plain HTML — anywhere that is not your WordPress site. Point its form at an endpoint and those leads join the same pipeline as the ones from your own site, tagged with their own source so you can tell the campaign apart.
Portals and referral partners
A portal, an iBuyer partner or a relocation company hands you an enquiry. Give each one its own endpoint and its own source label, and your reporting can finally answer which partner actually produces business.
Call answering and chat services
An answering service or an after-hours chat provider captures a caller at 9pm. The enquiry lands as a contact with the notes attached, rather than an email somebody has to retype in the morning.
Zapier, Make and n8n
Anything those tools can reach can now reach your CRM. If a platform has no direct integration but can fire a webhook, that is enough.
A custom front end
A headless site, a React app, a builder’s own microsite for a new development. The front end can be anything at all; the leads still land in one place.
An outside form behaves like one of your own
This is the part most inbound APIs skip. A submission arriving from another website runs through exactly the same handling as a form on your own site — nothing is treated as second class because of where it came from.
Leads come in. Updates go out.
Most inbound APIs stop at the first half. Your other systems need to hear about what happens next.
Four events worth acting on
A contact is created. A contact moves pipeline stage. A contact changes agent. A task is completed. Sending on every small edit produces noise, and noise is how an integration ends up switched off.
Keep the back office in step
A brokerage runs a transaction platform and an accounting system it will not replace. When a deal moves to Under Contract, those systems hear about it — without anyone re-typing a thing.
A trigger for everything else
Anything Zapier, Make or n8n can reach becomes reachable from MLS Genie. Slack alerts, spreadsheets, an ops board — without a purpose-built integration for each one.
Send everything, or almost nothing
The whole record by default, which is what most tools expect. Or record numbers and what changed only — no names, emails or phone numbers leave the site. The right answer depends on who is receiving it, so it is a switch rather than a decision we made for you.
Survives the other end going down
A failed delivery retries five times over about two hours, so a four-minute outage does not lose a lead. An address that fails twenty times in a row is switched off automatically rather than queueing work for ever.
Test before you trust it
One button sends a test event to any address. Nobody should have to wait for a real lead to find out whether the URL was typed correctly.
An open URL is an invitation. This is not one.
A public endpoint that accepts anything becomes a spam funnel within a week. Every endpoint here issues its own signing key and refuses anything it cannot verify.
“Did that form actually send anything?”
The question every integration eventually raises — answered without guesswork.
Every submission, recorded
Which endpoint it reached, when it arrived, whether it was accepted, and the fields it carried. When a partner insists they are sending leads, you can see for yourself.
Kept as long as you choose
Set a retention period and a nightly cleanup removes anything older, so the log cannot grow without limit on a busy site. It appears in the Cron Manager alongside every other scheduled job.
Treated as client data
Because it keeps the submitted fields, the log holds the names, emails and phone numbers people typed into your forms — and the Settings tab says so plainly, rather than leaving you to find out.
Ready to wire one up?
The developer documentation covers the endpoint address, the fields a submission can carry, how to sign a request, and what the activity log records.
Web Hooks questions answered
What are Web Hooks for?
Receiving lead data from external CRMs and lead platforms. You give a lead source your endpoint URL, and incoming submissions become CRM leads automatically.
What data can an endpoint accept?
Standard lead fields including first and last name, email, phone or mobile, message, source, type, and budget.
How is an endpoint secured?
Each endpoint issues its own signing key. The sending server signs every submission together with a timestamp, and the signature is checked before anything is stored, so a submission cannot be altered in transit or replayed later. Keys are held server-side, stored encrypted, and can be reissued at any time.
Can I see what came in?
Yes. The delivery log records each call with a timestamp, the endpoint, the status, and the ID of the lead that was created, with optional payload logging.
