Open House Follow-Up
The value of a viewing decays within about forty-eight hours. This workflow takes the sign-in, sends the brochure and floor plan the same evening while the property is still a picture in someone’s head, separates chain-free and mortgage-approved viewers from casual ones, and gives the vendor a viewing report by Sunday night rather than at the next weekly call.
What you get
Workflow blueprint
The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.
Getting it into Zapier
Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 7 steps, so it is a copy-and-paste job rather than a design job.
You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →
Not on Zapier?
An n8n workflow JSON ships with this template. Import it and all 7 steps arrive on the canvas wired in order, and 6 of the 7 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Every step maps to a native n8n node, one of them by a different route — see below.
Google Forms has no n8n node at all, so that step arrives as a native Google Sheets node on the form’s linked responses sheet. It is named for what it is on the canvas rather than for the app it stands in for, and the sticky note under it opens by saying so — the field names are unchanged either way, but the account you connect is the $Google Sheets one.
What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.
A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.
Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →
Setup steps
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Configure this step using the field mapping in the blueprint.
Implementation notes
- Same evening or not at all. A brochure that arrives on Tuesday for a Saturday viewing is competing with everything they have seen since.
- Answering the running-costs and inclusions questions before they are asked removes the most common reason a viewer goes quiet for a week.
- Ask what was wrong with it. Negative feedback is the only thing that improves the vendor conversation about price, and vendors trust it precisely because it is unflattering.
- Sending the vendor a report per viewing rather than per week is the single cheapest thing you can do to keep an instruction.