Automate with workflows and recipes
Install ready-made recipes or build workflows — trigger, conditions, actions, waits and branches — then test, publish and watch the run log.
Updated 5 Oct 2026
What you need
- Permission to manage automations (Owner or Admin by default)
- The Starter plan includes recipes; unlimited workflows need Growth or above
On this page
Workflows react to what happens — a new lead, a status change, a visit, a reply, a shortlist view — and do the routine work: send a WhatsApp, create a task, notify a manager, move a lead.
Start from a recipe
Settings → Automation → Recipes has ready-made workflows you install in one click and adjust:
| Recipe | What it does |
|---|---|
| Speed to lead | Welcomes every new portal lead on WhatsApp with top matches, alerts the team lead when nobody called within 10 business minutes, rotates the lead if still untouched |
| RNR retry ladder | After an unanswered call: call-back tasks, a “we tried calling you” WhatsApp, and Lost · Unreachable (or Nurture) after the set attempts |
| Hot signal | A client opens a shortlist again or spends real time on it: the owner is notified and gets a call task due in 15 minutes |
| Site visit reminders | Confirmation, 24 h and 2 h reminders with the meeting point, agent reminder, manager alert if nobody checked in |
| Post-visit follow-up | Liked it → Negotiation with similar options; otherwise a “show more options” task; nudges for missing feedback |
| New listing match alerts | Matching buyers hear about a new listing — one digest per buyer per day, consent checked |
| Price drop alerts | Buyers who viewed or liked a listing hear when its price drops by 3% or more |
| Owner freshness check | Asks owners every 14 days if the listing is still available; flags it stale without a reply |
| Rental renewal | Opens a renewal deal 60 days before an agreement ends; asks the manager at 30 days |
Build your own
- Go to Settings → Automation → Workflows and create one. Name it and choose what starts it (the trigger).
- Add conditions (“only when the source is 99acres and the budget is above ₹1 Cr”).
- Add steps: actions (send a template, create a task, assign, change status, notify, add tags…), waits (“10 business minutes” skip nights, Sundays and holidays), and branches (the first matching branch wins; records matching none take “Otherwise”).
- Test with a record — a dry run shows what each step would do, without doing it.
- Publish. Each publish is a version; you can go back to an earlier one.
Run log
Every run is recorded per record (lead, visit…) across versions, step by step — so you can see why a lead did or didn’t get a message. Pause a workflow to stop new runs (runs in progress continue when you resume); archive it to stop it for good.
Sign in to rate this article.
Related articles
- Follow-up plansSequences of WhatsApp, SMS, email, calls and tasks on a business-day clock, that pause when the lead responds.
- First-response SLAs and rotationMake sure every new lead hears from its owner in time — the SLA clock, at-risk warnings, rotation, second chance and the evening digest.
- Site visits with OTP verificationSchedule visits and tours, send reminders, verify the visit with the client's code at check-in, and record feedback or a no-show.
- Consent, DND, quiet hours and the TRAI 7-day windowThe rules PropZolo applies before any message goes out — consent, opt-outs, DND, the 7-day enquiry window, quiet hours and frequency caps.
Still stuck?
PropZolo support answers in the app and by email. Something down for everyone? Check the status page.