Recipes · by Amr Magdy · October 2026

15 automation recipes for a wholesaling CRM.

The automations that pay off first in a wholesaling CRM are a call task for every new lead, a callback for every missed call, required fields before a lead is passed, and long follow-up for “not now” leads. Here are 15 recipes written as trigger → action, which Salesforce tool to use for each, and the order to build them.

Short version

These are the automations I’d build first for a wholesaling team, written as trigger → action so you can hand them to whoever builds your CRM.
Count them before you pick an edition: Salesforce Professional allows 5 flows; Enterprise allows 2,000 active. source · source
Several are better as validation rules, approval processes or dashboard subscriptions than as flows.

15 automations for a wholesaling CRM

Automation	Trigger	Action	Fixes	Salesforce tool
New lead → owner and call task	Lead created	Assign by market or round robin; create call task due in 5 minutes; alert owner	Speed to lead	Record-triggered
Missed inbound call → callback	Call logged with outcome = missed, direction = inbound	Task due in 10 minutes for lead owner; if consented, send text	Missed calls	Record-triggered on Task
No activity in 7 days	Daily at 7am: open leads with last activity > 7 days	Follow-up task for owner; after 3 sweeps, flag for manager	Follow-up	Schedule-triggered
“Not now” → re-contact date	Status changes to Not now	Require re-contact date; create task on that date; enroll in long cadence	Long follow-up	Record-triggered
Warm/hot handoff check	Status changes to Warm or Hot	Block save without timeline, reason, condition, callback time (validation rule); task for acquisitions due same day / within 1 hour	Handoff	Validation rule + record-triggered
Offer above MAO → approval	Offer amount > MAO on the deal	Route to acquisitions manager for approval before status can be Sent	Offer discipline	Flow Approval Process
Offer expires	Daily: offers sent > 5 days with no response	Task to follow up; mark expired after 14 days	Offers	Schedule-triggered
Signed contract → under contract	Signed document written back by e-signature tool	Stage = Under contract; task for TC; post to #dispo	Contract to dispo	Record-triggered
Under contract → buyer match	Stage = Under contract	Create Deal Sent records for top 10 matching buyers; task for dispo	Dispo speed	Record-triggered
Closing date in 3 days	Daily: deals closing in 3 days	Checklist task for TC (title, funds, buyer confirmation)	Closing	Schedule-triggered
Deal dies → reason and source kept	Stage = Dead	Require dead reason; if “not now”, create re-contact date	Clean ROI	Validation rule + record-triggered
Fall-out → out of ROI	Contract cancelled	Uncheck “counts in ROI”; notify owner; reopen lead with reason	Honest reporting	Record-triggered
Duplicate seller → merge task	Duplicate rule alert on new lead	Task to merge; keep first lead source	Data quality	Duplicate rule + task
Proof of funds stale	Daily: buyers with POF date > 90 days	Task to request a new POF	Dispo	Schedule-triggered
Monday numbers	Monday 7am	Dashboard emailed to owner and managers	Weekly review	Dashboard subscription

Flow, validation rule or approval: which tool for which job?

Job	Tool	Why
Stop bad data being saved	Validation rule	Enforced everywhere, including imports and integrations
React to a change	Record-triggered flow	Runs when a record is created, updated or deleted
Sweep records on a timetable	Schedule-triggered flow	Runs at set times on batches of records
Guide a rep through a script	Screen flow	Shows only the questions that apply
Manager sign-off	Flow Approval Process	Multistep approvals with work items; Enterprise and up

Sources: Flow types · Flow Approval Processes.

Which automations should you build first?

Week 1

New lead task, missed call callback, warm/hot validation. These protect the leads you already pay for. See speed to lead and the handoff checklist.

Week 2

No activity sweep, not-now re-contact, dead reason. These protect the long follow-up where most conversions happen.

Week 3

Contract to dispo, buyer match, closing checklist. These shorten days to assignment.

Week 4

Offer approvals, fall-outs out of ROI, Monday dashboard. These make the numbers honest.

What goes wrong with CRM automation?

Building automations before the fields are clean: a flow that reads a free-text lead source does nothing useful.
Too many alerts: if every change pings someone, people mute them. Alert on exceptions only.
No owner: every automation should have a person who gets told when it fails.
Overlapping tools: a Zapier chain and a flow both creating tasks doubles the work. See replacing Zapier chains.

Questions

What should a wholesaler automate first in a CRM?

The new-lead call task, a callback task for missed calls, and required fields before a lead is marked warm or hot. They protect leads you already paid for.

How many flows can Salesforce Professional run?

Salesforce’s Professional Edition allocation page lists 5 flows. Enterprise and Unlimited allow 4,000 total and 2,000 active.

Should required fields be a flow or a validation rule?

A validation rule. It blocks the save everywhere, including imports and integrations, and can be conditional on stage or status.

Sources

Real estate CRM guide · Salesforce features · Integrations · Follow-up cadence builder · Offer follow-up in Salesforce · Appointment reminders and no-shows

Last updated October 2026. Product names, editions and limits change; check the linked source before you rely on one. Not legal advice.

Want these automations built and tested?

I build Salesforce for real estate investors and wholesalers, set up around how your team actually works. Start with a free 30-minute call or the fixed-price CRM Revenue Audit (USD 1,500).

Book a free 30-minute call See the Revenue Audit

Already on Salesforce? See a sample audit report. On Podio, REsimpli or GoHighLevel? See how a move to Salesforce works.

Or just ask one question about your setup: email · WhatsApp · LinkedIn