See llms.txt for all machine-readable content.
HOA architectural requests that no longer disappear into an inbox. This workflow takes each homeowner change request through an n8n Form, has AI summarize and flag it for the board, logs everything in Google Sheets, and keeps the owner and board updated by email until a decision is made.
Last updated: September 2026.
This workflow collects homeowners association architectural change requests via an n8n Form, summarizes and flags them with gpt-6-luna, logs everything in Google Sheets, and sends intake, decision, and deadline reminder emails through Gmail.
What happens right after a homeowner submits a request?
The form data is normalized, given a unique ARC ID with a timestamp and a 30-day review deadline, then sent to gpt-6-luna for advisory flags, a board summary, and an acknowledgment note. The request is logged to the ARC Requests sheet, the owner gets an acknowledgment email with the deadline, and the board gets a new-request notification.
What does the AI actually produce?
Advisory flags and a short board summary for the board notification and the Sheets record, plus an acknowledgment note that goes to the owner.
How do board decisions reach the homeowner?
Post the decision to the hoa-arc-decision webhook with arc_id and a decision of approved, conditions, or denied. The matching Google Sheets row is updated and the owner receives a decision letter by email; a malformed payload or an unknown ARC ID alerts the board instead.
What stops old requests from going stale?
A daily 07:00 run scans Google Sheets for pending requests due within 5 days and emails the board a reminder list.
Built with n8n. Need an assessment on your business? Feel free to reach out at https://khmuhtadin.com/consultation/