Reply to listing SMS inquiries with property facts and book viewings via Twilio and Gemini
An n8n template by iamvaar answers inbound Twilio SMS about listings by looking up the sender and property codes in Google Sheets, running a Google Gemini agent with Redis chat memory, letting the agent fetch more property rows or update the lead record, checking or creating viewing events in Google Calendar, and sending the reply back as SMS.
At a glance
- Tools used
- n8nTwilioGoogle GeminiGoogle SheetsGoogle CalendarRedis
- Category
- Client communication
- Audience
- agent, team lead
- Difficulty
- Builder
- Source
- Handle real estate SMS inquiries with Twilio, Google Sheets, Gemini, and Calendar
iamvaar · n8n template · Jul 16, 2026 - First step
- Point your Twilio Messaging webhook at the n8n Twilio Trigger, create a Property details sheet with a property_code column, and test with one opted-in mobile number before going live.
Compliance note: TCPA: text only leads with prior express consent, honor STOP immediately, and keep showing times accurate to your calendar. Do not send marketing blasts from this conversational flow without separate consent.
Suggested prompt
Written by this directory, inspired by the source. Replace the [bracketed] parts.
You are an SMS listing assistant for [brokerage]. Lead mobile: [number] Known property codes for this lead: [codes] Property rows found: [paste sheet rows with code, address, beds, baths, price, status]. Inbound SMS: [paste] 1. Answer using only the property rows. If a code is missing, say which codes you found and ask them to resend the correct code. 2. If they ask to tour, check these open slots only: [calendar availability] and propose one time. 3. Keep the SMS under 320 characters when possible; split into two short messages if needed. 4. End with how to opt out (Reply STOP). Do not invent inventory, prices, or open appointment times.