Skip to content
NEWMarketplace and your team: sell what you build, and get plans and changes that are tested before you see them. See what is new

Library / Documents, PDF & OCR

Documents, PDF & OCR

File water well completion reports with state APIs using OpenAI, Drive and Gmail

Runs when a driller's completion report arrives by webhook, checks annular grout depth and setback distances, enforces a cure hold with a post-cure re-check, then files the record and archives it in Google Drive.

What it does

📘 WORKFLOW DETAILS Water Well Drilling Contractor State Permit & Annular-Space Grouting Compliance Filer Value: turns a driller's field completion report into a state-filing-ready record — with real grout-depth and setback checks, a mandatory cure hold, and a post-cure re-check — instead of an office admin cross-referencing county code by hand. Who it's for: licensed water-well drilling contractors (or the compliance staff at a drilling company) who must file a completion report with the state water board after every well, and who need the annular-space grout depth and setback distances verified against county/aquifer-specific minimums before filing. How it works: 1. Field app POSTs the completion report to the webhook the moment drilling finishes. 2. Normalize shapes the raw payload into typed fields. 3. Research State Grouting Requirements (AI Agent with a real lookup tool) calls the state grout-minimum API for this county/aquifer type and returns strict JSON minimums — never guessing from memory. 4. Check Grouting & Setback Compliance (Code) compares the actual grout depth, septic setback, and property-line setback against those minimums, and checks driller license expiry. 5. License Valid & Setbacks Met? branches: failures go straight to Tag Non-Compliant; passes proceed to a mandatory 48-hour grout cure hold (state code requires cure time before final inspection). 6. After the hold, Fetch Post-Cure Inspection Reading pulls the county's re-measured grout depth; Verify Post-Cure Grout Level checks it against the same minimum with a 1ft tolerance. 7. Post-Cure Grout Level Acceptable? branches again into Tag Cure Failed or Tag Filing Ready. 8. All three outcomes converge at Shape Filing Record (single source of truth), then file to the state portal, archive to Drive, and email the driller + regulator with the final status. Node summary: Webhook → Set (normalize) → AI Agent+Tool+Chat Model (grout-minimum research) → Code (compliance check) → If (license/setback gate) → Wait (48h cure) → HTTP Request (post-cure reading) → Code (cure verification) → If (cure gate) → Set×3 (tag outcomes) → Set (shape) → HTTP Request (state filing) → Google Drive (archive) → Gmail (notify). Input: webhook JSON {driller_license_no, driller_license_expiry, well_id, county, aquifer_type, grout_depth_ft, setback_to_septic_ft, setback_to_property_line_ft, total_well_depth_ft}. Output

The steps

  1. Receive Well Completion Report
  2. Normalize Completion Report
  3. State Grout Minimum Lookup Tool
  4. Agent Model
  5. Research State Grouting Requirements
  6. Check Grouting & Setback Compliance
  7. License Valid & Setbacks Met?
  8. Tag Non-Compliant
  9. 48-Hour Grout Cure Confirmation Hold
  10. Fetch Post-Cure Inspection Reading
  11. Verify Post-Cure Grout Level
  12. Post-Cure Grout Level Acceptable?
  13. Tag Cure Failed
  14. Tag Filing Ready

18 steps in total.

Similar automations