Listings

Every morning, n8n compares each listing's days on market, enquiries, viewings, and offers against your portfolio medians and posts a Gemini diagnosis of the stale listings to Slack

An n8n template by iamvaar runs every day at 8:00 AM and reads all listing rows from a Google Sheets Listings spreadsheet. A code step calculates days on market and enquiry-to-viewing-to-offer conversion for each listing, compares each listing to the portfolio medians, and flags listings that are underperforming (or flags rows with missing data), with a 7-day cooldown between alerts and a 10-day grace period after a price change. The workflow writes the latest enquiries, viewings, and offers back to the sheet so trends can be tracked. For each flagged listing, Google Gemini returns a JSON diagnosis with the likely issue, a suggested action, and a severity. The workflow posts the alert to a Slack channel (escalating repeat flags and optionally mentioning the listing agent and a manager) and records the alert date, issue, action, and alert count back in the Google Sheets row. If the workflow fails, a Slack message names the failed node and the error.

At a glance

Tools used
n8nGoogle SheetsGoogle GeminiSlack
Category
Listings
Audience
team lead, broker, listing coordinator
Difficulty
Builder
Source
Triage stale property listings with Google Sheets, Gemini, and Slack
iamvaar (n8n creator) · n8n template · Sep 10, 2026
First step
Build a Listings sheet with the template's columns (Listing ID, Property, Status, Listed Date, Enquiries, Viewings, Offers, Last Price Change Date, Last Alert Date, Alert Count, Agent Name, Agent Slack ID, and the Prev snapshot columns), connect a Google service account, a Gemini API key, and Slack in n8n, then run the workflow once against last week's numbers to see which listings get flagged.

Compliance note: Use the Gemini diagnosis as a prompt for a conversation with the listing agent, not as advice to send to the seller, and keep the listing data you send to Gemini to the numbers and property details the workflow needs.

Suggested prompt

Written by this directory, inspired by the source. Replace the [bracketed] parts.

Here is one listing flagged as underperforming, with its days on market, enquiries, viewings, offers, last price change date, and the portfolio medians for the same numbers. Return JSON with three fields: likely_issue (one sentence naming where the listing loses buyers: too few enquiries points to price or marketing, enquiries without viewings points to photos or description, viewings without offers points to condition or price), suggested_action (one concrete step the listing agent can take this week), and severity (low, medium, or high, with high only if the listing is more than double the median days on market). If the data looks incomplete, say which field is missing instead of diagnosing. Listing data: [paste]

Share on X Read the source

← All use cases