Parse portal lead emails from Gmail into scored HubSpot deals with Gemini
An n8n template by Hassan watches a Gmail label for property-portal lead notifications (Zillow, Realtor.com, Redfin, and others), uses Google Gemini to extract name, contact info, property interest, budget, and timeline, scores the lead hot/warm/cold, sends an acknowledgment email, creates or updates a HubSpot contact and deal in the matching pipeline stage, logs to Sheets and Airtable, and alerts the agent on hot leads.
At a glance
- Tools used
- n8nGmailGoogle GeminiHubSpotGoogle SheetsAirtable
- Category
- Lead follow-up & inside sales
- Audience
- agent, team lead
- Difficulty
- Builder
- Source
- Qualify inbound real estate leads from Gmail with Gemini and HubSpot
Hassan · n8n template · Jul 16, 2026 - First step
- Create a Gmail filter that labels portal lead emails n8n-leads, connect Gemini and HubSpot credentials in n8n, and run one labeled test email with Gmail send nodes disabled until scoring looks right.
Compliance note: Honor portal and CRM privacy rules. Do not auto-text a lead until you have consent for SMS. Keep acknowledgment emails factual; do not promise availability you have not checked.
Suggested prompt
Written by this directory, inspired by the source. Replace the [bracketed] parts.
Parse this property-portal lead notification email into structured fields. Email body: [paste]. Return JSON with: lead_name, lead_email, lead_phone, property_interest, budget, timeline, portal_source, lead_score (Hot|Warm|Cold), score_reasoning (1 sentence), acknowledgment_email (under 120 words confirming we received the inquiry and naming the property if present). Scoring rules for my market: Hot = ready to tour within 2 weeks or pre-approved; Warm = 30–90 day timeline; Cold = researching or no timeline. Do not invent contact fields that are missing from the email.