See llms.txt for all machine-readable content.

Back to Templates

Nurture real estate leads from Follow Up Boss signals with Claude and Gmail

Created by

Created by: Max || maxzeshut
Max

Last update

Last update 8 hours ago

Categories

Quick overview

Watches for real reasons to write (a new listing that fits, a rate change, an anniversary, a calendar gap) and has Claude draft a short, specific message in your voice for each long-term lead in Follow Up Boss, kvCORE or HubSpot. You approve, Gmail sends, the CRM logs.

How it works

  1. Runs on a schedule to start a lead-nurture cycle based on new signals and your configured rules.
  2. Matches leads to the relevant signal (for example, a listing fit, a rate change near their budget edge, or a personal date).
  3. Applies guardrails to exclude leads who were contacted recently, unsubscribed, are in an active conversation, or are already in an active CRM stage.
  4. Uses Anthropic Claude to draft a short message (and optional subject) grounded in the provided lead context and flags low-confidence or policy-sensitive drafts for human review.
  5. Routes flagged drafts to a review queue, and sends the rest to Slack for approve/reject confirmation.
  6. Sends approved messages via Gmail using the generated subject and draft content.
  7. Watches for incoming Gmail replies and appends a reporting row to Google Sheets.

Setup

  1. Add Anthropic (Claude), Slack, Gmail, and Google Sheets credentials in n8n.
  2. Update the values in “Config (edit me)” (name, email, timezone, quiet hours, approver, and test/approval modes) and set the Slack approver channel.
  3. Ensure the workflow input includes each lead’s email address (or map it into the Gmail send step) and adjust the Google Sheets spreadsheet ID and sheet name used for reporting.

Requirements

  • n8n 1.x (tested on 2.38), an Anthropic API key for the Claude nodes, and Follow Up Boss / kvCORE / HubSpot, Gmail / Outlook, Slack (or their equivalents — the nodes are standard and easy to swap).

Customization

  • Set the signal types and your voice rules in the Config node; swap Follow Up Boss for kvCORE or HubSpot. Keep the guardrail: No message without a reason the lead would recognise; the model cannot invent one.

Additional info

One of 48 Agentmelt blueprints. The blueprint page explains the trigger, the steps, the guardrails and where the standard version stops: https://agentmelt.com/workflows/lead-nurture-automation/ — all 48 workflow files are on GitHub (MIT): https://github.com/zeshutmax/agentmelt-blueprints