This page requires JavaScript to display.
The Nolan Scott Team Sells and buys businesses from $1M to $15M+, and advises on the real estate that comes with them. nolanscottteam.com →
Example 03 / 18 · a sample from our Rolodex of 100+ automations Make.com
Automation Breakdown · Make.com Scenario Pair

Listing Scraper and Deal Matcher, Ingest, Match & Draft

Two Make.com scenarios that run as one machine. Every day the first pulls new business-for-sale listings from the alert emails you already subscribe to, scrapes the full details, and builds a listing Rolodex, then matches every listing against each buyer client’s buy box. The second wakes up, reads the fresh matches, and drafts the outreach: a personalized email per hot match and a daily digest.

2 scenarios, one chain
every listing scored per buyer
5 Claude calls
0 listings scraped twice
True AI automation isn’t one clever workflow. It takes 20 to 40 workflows working together to make a real impact on a business. That’s what we do: a Rolodex of 100+ automations across different CRMs and platforms, ready to be custom-built for your specific CRM and software stack.
The Workflow
One long chain, left to right · click any module for its explanation
NEW
KNOWN
MARK PROCESSED
MATCH BUYERS
SCENARIO 2
NO DRAFT YET
HOT MATCH
DIGEST
Two scenarios, one machine
Scenario 1 ingests and matches; Scenario 2 wakes up on its own schedule and drafts. They piggyback off the same sheets and data store, so they read here as one chain.
The Rolodex
Every listing ever seen lives in the data store and the sheet. The dedup gate means nothing is scraped, scored, or drafted twice.
Matching, not just alerting
Alerts tell you a listing exists. This scores it against every buyer’s buy box, so each client only hears about deals rated for them.
M
Gmail
search alert emails
A\
Anthropic Claude
extract listing links
≡
Iterator
one listing each
DB
Data store
seen before?
≫
Skip
already known
FC
Firecrawl
scrape the listing
A\
Anthropic Claude
normalize fields
DB
Data store
add / replace record
GS
Google Sheets
add to Rolodex
AA
Array aggregator
collect the batch
+
Router
close loop + match
M
Gmail
update email labels
GS
Google Sheets
load buyer roster
AA
Array aggregator
bundle clients
≡
Iterator
per listing
≡
Iterator
× per client
A\
Anthropic Claude
score the match
GS
Google Sheets
write match row
GS
Google Sheets
Drafter: read matches
≡
Iterator
one match each
GS
Google Sheets
draft already exists?
DB
Data store
get listing record
GS
Google Sheets
mark drafted
AA
Array aggregator
bundle the day
+
Router
draft vs digest
A\
Anthropic Claude
write outreach draft
M
Gmail
create draft email
C
Close CRM
log note activity
Tx
Tools
text aggregator
A\
Anthropic Claude
write daily digest
M
Gmail
send digest
◈
The machine at a glance
Click any module to see exactly what it does. The chain reads left to right: ingest and dedup new listings, score them against every buyer, then the Daily Drafter turns fresh matches into outreach drafts and a digest.
Gmail
Anthropic Claude
Firecrawl
Data store
Google Sheets
Flow control
Tools
Close CRM
How It Works

Every listing, scored for every buyer, drafted daily

01 · Ingest
Alert email to Rolodex

Listing alert emails land in Gmail; Claude extracts the listing links, and each one is checked against the data store, anything already known skips instantly. New listings get scraped in full by Firecrawl, normalized by Claude into structured fields (price, SDE, industry, location), and written to both the data store and the Rolodex sheet.

02 · Match
Scored against every buy box

The router closes the loop, processed emails get relabeled, and fans into matching: the full buyer-client roster is pulled from Sheets, and Claude rates each new listing against every client’s criteria, producing a scored match row per pairing. The buy box does the filtering; the score does the ranking.

03 · Draft
The Daily Drafter wakes up

On its own schedule, scenario two reads the fresh match rows, skips anything already drafted, and splits: hot matches get a personalized Claude-written draft email in Gmail plus a note logged to Close CRM; the rest roll up into a Claude-written daily digest. Drafts wait for review, the digest sends itself.

Next example: YP Prospector →
AI · nolan scott team
Unpacking...