Can you contact me when you can?
Thanks,
Hey Mark, happy to. I’m in California, Pacific time.
Tomorrow morning is good for me, 9:00, 10:00 or 11:00 are all open. Tell me which one works and what time zone you’re in. And if none of those fit, just tell me what time is good on your end and I’ll see if I can make it work.
If it’s easier, you can also grab any open slot here: https://calendar.app.google/idpo4m7u1u6Ebmeo7
One thing that would help before we talk, if you can send a screenshot of the scenario and the output of the MLS module from a run that didn’t work, I’ll come in already knowing where it’s stuck instead of us spending the call finding it.
Cindy
Hi Mark,
I saw you’re still actively working through the MLS/Google Maps scenario.
Rather than trying to solve the whole valuation model upfront, I’d start with one failing property request and trace it end-to-end:
website webhook → address/Maps data → MLS request → field mapping → report response.
My strongest background is API/webhook integrations, JSON/data mapping, validation and workflow reliability. I haven’t worked with your specific MLS provider, so I’d rather prove the fit on one bounded technical issue than overstate that experience.
I can offer a $100 fixed first diagnostic/repair milestone: identify the failing step, fix one agreed API/mapping path where feasible, test it against a normal case plus one missing-data/error case, and hand over the corrected workflow with short notes.
Relevant systems work:
If this is still useful, which MLS provider are you using, and is the current scenario failing with an error or completing with an incorrect/empty report?
Best,
Mahdi
Hi Mark — I’m an AI/automation engineer with a degree in Architecture and Urbanism. That combination is useful here: I can examine both the property logic and the API/webhook path instead of treating this as only a Make configuration issue.
I can start with a $100 fixed diagnostic, credited toward the implementation:
- inspect the current scenario and redacted execution bundles;
- trace website form → address normalization/geocoding → MLS query → Webhook Response;
- define one defensible ruleset for one market and property type;
- test five cases: valid property, no match, multiple comps, incomplete address, and API failure;
- deliver findings plus a fixed completion scope within 48 hours of receiving the materials.
My verifiable work is in Python/FastAPI/n8n API workflows with validation, retries, deduplication, and human review. I won’t claim a prior production MLS deployment; my Architecture and Urbanism background is the relevant domain advantage.
Which MLS API are you using, and does the current scenario error, return empty results, or produce implausible values?
LinkedIn: https://www.linkedin.com/in/kevin-gontijo/
Email: [email protected]
Mark, is this still open as a paid project? Which MLS API are you using, where does the current scenario fail, and what budget and deadline do you have? I’d propose a fixed-price first stage around one anonymised property example: webhook → Google Maps → MLS → report, checked against your agreed valuation rules and expected output. I’d quote it after reviewing that example and keep the bot separate. Please don’t post API keys, private MLS records or client data here.