High-volume real-estate direct mail: raw property data → dedup → suppression → physical mailings, with full tracking.
A real-estate operator pulls owner/property data from PropStream and wants to send physical mailings via Lob, tracked in an Airtable CRM. The risky parts aren't the API integrations — they're deduplication (don't pay to mail the same owner twice this month) and suppression (don't mail anyone who said stop).
A Make scenario that ingests PropStream exports, normalizes addresses, deduplicates against the Airtable CRM with a configurable lookback window, applies the suppression list as a hard gate, then submits the surviving batch to Lob and writes Lob's tracking IDs back to Airtable. Webhooks from Lob update delivery state per mailing.
Operator runs the full ingest → mail → track loop without hand-checking any of the dedup or suppression edges. Spend per mail batch is predictable; mailings to suppressed addresses are mechanically impossible, not policy-dependent.
PropStream gives messy address strings. Without USPS-style normalization upstream of dedup, the same property shows up as three records. The scenario normalizes first, then dedups against the normalized field — not the raw input.
Suppression isn't 'usually applied' — it's a gate the batch can't get past. If the suppression lookup fails (API down, table missing), the scenario aborts instead of sending. Quiet failure here = legal exposure.
Every submitted piece writes its Lob ID back to the CRM row so operator can see 'in transit / delivered / returned' inline. No separate dashboard to check.
Run the free 5-minute diagnostic — I'll tell you whether it's a $0 weekend project or a 2-week build.