The three automations a 12-deal real estate agent actually needs
Three automations. Not thirty.
That's the entire prescription on this page. If a "real estate AI workflow" listicle handed you 27 Zaps and a vague promise about your business running while you sleep, close the tab. The math doesn't work at the median agent volume, and the listicle's author has never had a Gmail OAuth token expire on a Friday at 4:30 PM.
The wrapper-stack listicle problem
Most "real estate workflow automation" articles tell you to wire 30 Zaps your first weekend on Zapier. Lead-routing. Drip sequences. CRM sync. Birthday cards. Three different "nurture" campaigns. A Google Sheet that auto-updates from a Typeform nobody fills out.
Here's what actually happens. A token expires — Gmail, Compass One, Dotloop, the MLS partner, pick one. The Zap fails silently. By month four, 30% of zaps in a typical agent's stack are dark. The thing the agent bought to remove cognitive load just replaced it with a different cognitive load: is my stack still alive?
The 27 automations on the listicle aren't time-savers. They're debug debt with marketing copy on top.
What this page does instead
I'm going to show you the three automations that earn their keep at the median deal volume — and exactly what to wire in Zapier or Make.com for each. About 30 minutes of setup, total. One-time.
Before you wire any of this, confirm you've crossed at least one of the three thresholds on the pillar — 30 sides a year, $500/mo paid leads, or a second human on the deal. If you haven't, the foundation-model paste workflow is the right move. Same setup time, $20 versus $30, zero OAuth tokens to rot.
If you've cleared a threshold, here are the three.
Automation 1 — New inbound lead → instant SMS to me + first-touch reply
The job: hit the 5-minute Lead Response Management window automatically, every time, even when you're in a showing or a kid pickup line. Oldroyd's MIT/InsideSales study of 15,000 leads pegs the math: a 5-minute response is 21x more likely to qualify than a 30-minute response. Industry average inbound response is 42 hours. This Zap closes the gap to under 60 seconds.
What you'll need
- Zapier Pro at $19.99–$29.99/mo, or Make.com Core at $10.59/mo
- A Twilio sub-account for the SMS leg (~$1/mo plus $0.0079/SMS)
- Your Gmail where Zillow / Realtor.com / Compass One paid leads land
- A Gmail filter that labels those emails — "Zillow Lead", "Realtor.com Connection", "Compass Paid"
- One drafted first-touch email template
Setup time — about 12 minutes
Steps
- Create the Gmail filter first. Search for the Zillow Flex sender address (
flex@zillow.com for most accounts), click the search dropdown, "Create filter," apply label "Zillow Lead." Repeat for leads@realtor.com and your Compass One lead address. The Zap can't trigger if the label isn't there.
- Create the Zap. Trigger app: Gmail. Trigger event: "New Labeled Email." Pick the "Zillow Lead" label. Test the trigger with a real lead email so Zapier sees the data shape.
- Action 1 — Twilio Send SMS. From: your Twilio number. To: your cell. Body:
New {{label}} — {{from_name}}, {{subject}}. First 3 lines: {{body_plain | truncate: 200}}. That gives you the lead's name, the property they asked about, and enough body to know what to say next.
- Action 2 — Gmail Send Email. To:
{{from_email}}. Subject: Re: {{subject}}. Body: paste your first-touch template — two specific time windows for a call, your Calendly link, the TREC "working with another agent" question, the pre-approval ask. Voice-match it to your Context Card so it doesn't read like a bot.
- Publish, test, duplicate. Send a test email with the matching label. Confirm the SMS lands and the reply sends. Duplicate the Zap for the Realtor.com and Compass labels — same actions, different trigger label.
A Zillow lead lands at 11:47 PM Saturday. Your phone buzzes by 11:47:30. The lead gets your reply by 11:47:45 with two windows for Sunday. The 5-minute window is hit while you're asleep. The thing that can break is the Gmail filter — if Zillow changes their sender address, the label stops applying. Check it weekly.
Automation 2 — Showing booked → calendar block + 30-min reminder
The job: when a buyer books a showing through your Calendly, the property gets blocked on your calendar with the address attached, and you get a reminder SMS 30 minutes before with parking notes. No more pulling up Calendly in the truck to remember which house you're driving to.
What you'll need
- Same Zapier or Make.com plan as Automation 1
- Calendly (any tier with webhooks — the $10/mo Standard plan is fine)
- Google Calendar and your Twilio account from Automation 1
- A Calendly event type called "Showing" with a custom question for the property address
Setup time — about 8 minutes
Steps
- Create the Calendly event type. Add a new event type, "Showing." Custom question: "Property address you'd like to see." Duration 45 minutes. Buffer time 15 minutes after — that's the drive-to-the-next-thing margin.
- Create the Zap. Trigger app: Calendly. Trigger event: "Invitee Created." Filter on event type = "Showing" so only showings fire this Zap.
- Action 1 — Google Calendar Create Detailed Event. Title:
Showing — {{invitee_name}} at {{custom_question_property_address}}. Start/end times from the trigger. Location: {{custom_question_property_address}} — this is the magic field. Google reads the address and turns it into a Maps link automatically. Description: invitee email and phone so you can call from the truck if you're running late.
- Action 2 — Delay Until + Twilio SMS. Use Delay by Zapier set to
{{event_start_time}} minus 30 minutes. Then Twilio Send SMS: Showing in 30 — {{custom_question_property_address}} with {{invitee_name}}. Maps: https://maps.google.com/?q={{custom_question_property_address | url_encode}}. Parking: [your standard note].
- Test with a real booking. Book yourself, confirm the calendar event creates with the address as Location, confirm the SMS lands 30 minutes before.
The Wilsons book a 1 PM Saturday showing at 142 Lakeshore. At 12:30 your phone buzzes: "Showing in 30 — 142 Lakeshore with Wilsons. Maps link. Parking: church lot on the lake side, the front fills up by 12:45." You leave at 12:35. The thing that breaks: Calendly occasionally renames the custom question field. If your Maps link prints {{custom_question_property_address}} literally, re-map the Location field and save.
Automation 3 — Contract executed → key dates on your phone calendar
The job: the moment a contract gets executed in Dotloop, Skyslope, or DocuSign, every deadline that matters drops into your phone calendar as a real event with reminders. Option period end, financing contingency end, inspection deadline, appraisal deadline, closing. Five events, each with reminders the day before and the morning of.
This is the one most agents botch by hand. The dates land on a sticky note, the sticky note migrates to a contract folder, and the option period closes Tuesday afternoon while the agent is at a different listing.
What you'll need
- Same Zapier or Make.com plan
- Dotloop (most common in TN), Skyslope, or DocuSign — whatever your brokerage uses
- Google Calendar
- The contract field names for your platform — you need the API field that holds option-period-end and so on
Setup time — about 10 minutes
Steps
- Confirm your contract field names. In Dotloop, click each date field in your contract template and grab the field name from the right panel —
OptionPeriodEndDate and the rest. Write down all five.
- Create the Zap. Trigger app: Dotloop (or Skyslope, or DocuSign Connect). Trigger event: "Loop Submitted for Review" or "Document Fully Executed." The exact trigger varies by platform. The point: fires once, when all parties have signed.
- Action 1 — Google Calendar Create Detailed Event. Title:
Option period ENDS — {{property_address}}. Date: {{OptionPeriodEndDate}}. All-day. Reminders: 24 hours before AND 9 AM the day of. Description: buyer, seller, closing date.
- Actions 2-5 — repeat for the other four dates. Same setup, swap the title and date field. Financing contingency end, inspection deadline, appraisal deadline, closing. All five become real calendar events with reminders.
- Test with a throwaway contract. Confirm five events appear with right dates and reminders push to your phone.
The Wilsons go under contract Tuesday at 4 PM. By 4:01 your calendar has five new events. Wednesday at 9 AM your phone reminds you option period ends Friday. Friday at 9 AM your phone reminds you it ends today. The deal doesn't fall apart because a sticky note got laundered. The thing that breaks: date format mismatches. If Dotloop sends MM/DD/YYYY and Google Calendar expects YYYY-MM-DD, you'll get a Zap error. Add a Formatter by Zapier step between trigger and Google Calendar, set to Date/Time with explicit input and output formats. Wire it once.
What it costs and why these three pay
Three automations. Roughly 30 minutes of one-time setup. Zapier Pro at $19.99–$29.99/mo, or Make.com Core at $10.59/mo if you'd rather save money and learn a slightly steeper UI. Twilio runs $5–$10/mo at this volume. Total: $25–$40/mo for three workflows that genuinely save time forever. The typical "real estate AI workflow" listicle recommends 27 more Zaps at the same monthly cost — ten times the setup time, 30% of them dark by month four.
For the head-to-head on tooling, see Zapier vs Make.com vs the foundation-model approach.
Here's the technical reason these three pay and the other 27 don't. In What We Learned from a Year of Building with LLMs — Part I — Yan, Husain, Bischof, Frye, Liu, and Shankar, O'Reilly, May 2024 — the authors are explicit: "Small tasks with clear objectives make for the best agent or flow prompts." They cite AlphaCodium going from 19% to 44% on CodeContests through decomposition. Each decomposed step was deterministic. The model never had to decide what to do — only when.
The three automations on this page share that property. New lead arrives, send the SMS, send the reply. Showing booked, block the calendar, send the reminder. Contract executed, drop the five dates. No judgment calls. No drift. No drift means no debug surface, and no debug surface means it stays running.
This is also why the weekly verification habit matters. Simon Willison's 2025 weblog sums up the underlying shift: verification is now the expensive part. The model can draft fast — what costs you is making sure the draft is right. A Zap that runs unsupervised has no verification step at all. Every Friday morning, ten minutes, walk the stack. Run a test through every Zap. That's the debug tax — and the only way to keep these three from rotting at month four.
The same logic shows up in Karpathy's "vibe coding" framing on X — fine for low-stakes prototypes, dangerous when the output goes straight to a client without a human eye on it. The verify-then-send loop on these three Zaps is the realtor's version of that discipline. The Zap drafts, you check, you ship.
The 27 on the listicle fail this test. The "AI agent that handles your follow-up" pitch needs the model to decide what to say, when to say it, and whether to say anything at all. Those are judgment calls. Real-estate follow-up is non-deterministic. The research says agents don't reliably handle non-deterministic workflows yet.
Three deterministic, judgment-free automations beat thirty judgment-heavy ones. Every time.
When this DOESN'T work
Even these three might be overkill. Pulled directly from the three thresholds on the pillar:
- Below 30 closed sides a year. NAR median is 10. At the median, the volume isn't there to justify the maintenance tax. Three Zaps still cost you 30 minutes plus monthly checks plus the inevitable token re-auth.
- Below $500/mo in paid lead-gen spend. If your pipeline is sphere and referral, the LRM 5-minute window is something you hit by checking your phone. Your sphere already trusts you.
- Below 2 humans on the deal. Solo operator with no TC, no buyer's agent, no admin? Your Notes app and Calendar are the system of record. Adding Zapier adds a second system that has to stay in sync. That's friction, not removal of friction.
If you're below all three, run the foundation-model phone-first workflow instead. Same outcome on follow-up speed. Half the cost. Zero OAuth tokens to rot.
If you've cleared at least one threshold, wire these three this Saturday. Skip everything else.
Sources
Primary data
Independent builder/operator creators
Vendor pricing (pricing pages only, no vendor blogs cited)
Last updated 2026-04-29.
Schema (HowTo, three step groups)