The Make.com storm lead scenario is an 8-module pipeline that detects a storm event and delivers the first homeowner contact within 14 minutes — with no human involvement from trigger to voicemail drop. Here is the full scenario architecture and how to build it.
Module 1: Schedule Trigger
A Schedule module polls every 30 minutes. This is the heartbeat of the entire system — every 30 minutes, it checks HailTrace for new qualifying events in monitored territories. The interval can be shortened to 15 minutes for markets with active storm seasons.
Modules 2 Through 8
Module 2 (HailTrace API): HTTP Request to the HailTrace weather events endpoint with your territory coordinates and minimum hail size filter. Module 3 (ATTOM Data): HTTP Request to ATTOM's polygon property search, passing the storm swath GeoJSON from Module 2. Returns all properties inside the damage zone. Module 4 (BatchSkipTracing): HTTP Request to skip trace each property record — appending verified mobile phone and email. Module 5 (AI Scoring): OpenAI API call per property to generate the 0-100 priority score. Module 6 (GoHighLevel): GHL API calls to create contact records and pipeline opportunities for all qualified leads. Module 7 (Twilio): Twilio API calls to initiate voicemail drops to the top 50 scored properties. Module 8 (Google Sheets): Write all lead data, scores, and outreach timestamps to a Google Sheet for reporting and deduplication. The full animated Make.com scenario — with all eight modules and animated data flow — is in the Storm Lead AI Machine demo.