Permit Lead Automation
New septic permit applications across 7 Central Texas counties are automatically scraped, enriched with contact data, and pushed into GoHighLevel every morning.
System Overview
How permit data flows from public records to your CRM. Click any box to open that service.
Pipeline Steps
Click each step to see exactly what happens. Links at the bottom of each step let you open the relevant service directly.
Step 1 — Scrape Permit Applications
The pipeline begins by visiting MGO Connect, the Texas Commission on Environmental Quality's (TCEQ) online portal for On-Site Sewage Facility (OSSF) permit applications.
Our scraper checks for new permit applications across 7 Central Texas counties:
A baseline comparison ensures only permits that haven't been seen before are processed. This prevents duplicate contacts and wasted API calls.
Step 2 — Enrich with Contact Data
Each new permit's property address is sent to the BatchData Skip-Trace API, which searches public records and data sources to find the property owner's contact information.
What gets enriched:
- Owner Name — first and last name of the property owner
- Phone Numbers — up to 3 phone numbers (mobile prioritized)
- Email Addresses — up to 3 email addresses
- Mailing Address — owner's mailing address (often different from property)
About ~20% of permits can't be enriched — typically new construction on vacant land with no prior owner records. These contacts are still created and tagged Unenriched - Needs Retry for later processing.
Step 3 — Create CRM Contact
Enriched lead data is pushed into GoHighLevel (your CRM) as a new contact, including all available data from enrichment.
Contact record includes:
- Name — owner's full name (or permit placeholder if unenriched)
- Phone & Email — primary contact methods from BatchData
- Address — owner's mailing address
- Tags —
OSSF Permit Lead+ county-specific tag - Source —
MGO OSSF Permit Scraper
If a contact already exists (matched by phone or email), the system backfills missing fields rather than creating a duplicate.
Step 4 — Create Sales Opportunity
For every new contact, a sales opportunity is created in your GoHighLevel pipeline so the team can track leads through the sales process.
Opportunity details:
- Name — includes the permit application number and address
- Pipeline — placed in the "New Permit Leads" pipeline
- Stage — starts in the first stage, ready for outreach
- Property Address — stored on the opportunity for quick reference
The sales team can open GHL each morning and immediately see new leads in the pipeline, ready for a call or text.
County Coverage
Hover or tap a county on the map to see its permit lead metrics. Data accumulates as the automation runs daily.
Frequently Asked Questions
Unenriched - Needs Retry. When the data becomes available (e.g., after closing), a backfill run can automatically update them.
Technical Details
For the technically curious — here's what's under the hood.
15 12 * * * UTC = 6:15 AM CST). The workflow can also be triggered manually via workflow_dispatch with options for run mode (normal / backfill). All secrets (API keys) are stored in GitHub Secrets — never in code.
GoHighLevel API — contacts are created/updated via the
/contacts/upsert endpoint, and opportunities are created via /opportunities. Tags, custom fields (including property address on opportunities), and pipeline assignment are all managed through the API.
state/ directory for auditing. View run history on GitHub Actions.