PropertyFinder

Overview

Ruby connects directly to PropertyFinder's Atlas API for two-way publishing, real-time lead capture, and self-serve webhook management. Tokens auto-refresh on expiry — you'll never re-authenticate. Detailed rejection reasons surface inside Ruby, so when a listing fails PF review you see exactly why (missing photos, invalid permit, short description) and fix it on the first try.

How to set up

1. 1

   Get your API Key and API Secret from PropertyFinder Enterprise (your account manager provisions these).

2. 2

   In Ruby, go to Settings → Portal Integrations → PropertyFinder, paste both, and click 'Test Connection' — Ruby returns your live listing count.

3. 3

   Click 'Import Listings + Portal Agents'. Ruby pulls everything currently live on PF and matches agents by email.

4. 4

   In the Webhooks panel, click 'Subscribe' on lead.created, lead.updated, and lead.assigned events — Ruby manages PF webhooks for you in-product.

5. 5

   Click 'Sync Leads' to backfill the last 90 days. From there, new leads stream in automatically.

Benefits

• Set up once inside Ruby — no PropertyFinder dashboard visits, no support tickets, no waiting on portal admins
• Stays connected on its own — you'll never be asked to reconnect or re-enter credentials
• Primary Plus leads arriving on WhatsApp become complete lead profiles — name, phone, budget, bedrooms — without anyone typing
• When PropertyFinder rejects a listing, Ruby shows you the exact reason — fix it on the first try instead of guessing
• Calls are recorded and written out for you automatically — and Ruby knows whether the call was actually answered
• A full history of every import — see exactly what came in and when

Why it matters

PropertyFinder drives the highest-intent buyer traffic in Dubai and Abu Dhabi. Every minute a PF lead waits is a minute your competitor closes them. Ruby's webhook self-serve + token auto-refresh means your PF pipe never stops flowing — no expired-credential incidents, no portal admin tickets, no missed leads.