---
title: GoHighLevel Form Automation Failure — Reynolds
type: article
created: '2026-03-04'
updated: '2026-03-04'
source_docs:
- raw/2026-03-04-weekly-call-w-melissa-127255244.md
tags:
- reynolds
- gohighlevel
- automation
- monitoring
- technical-debt
- google-sheets
layer: 2
client_source: Reynolds Transfer and Storage
industry_context: b2b-services
transferable: false
---

# GoHighLevel Form Automation Failure — Reynolds

## Overview

A form submission automation for [[wiki/clients/current/reynolds/index|Reynolds]] stopped working, causing form data to silently fail to reach the client's Google Sheet. The client discovered the failure themselves and reported it — no internal monitoring was in place. Mark diagnosed and resolved the issue during the 2026-03-04 weekly sync.

## Root Cause

GoHighLevel's Google integration breaks on a recurring ~30-day cycle. This is a **known GoHighLevel issue**: Google does not fully trust GoHighLevel's OAuth integration and periodically revokes the connection. When the connection drops, GHL displays a warning banner in the Integrations panel, but no outbound alert is sent to account administrators.

The integration failure was silent from the client's perspective — the form itself continued accepting submissions normally. Only the downstream automation (writing rows to Google Sheets) was broken.

## Compounding Issues

Several structural problems made diagnosis significantly harder than it should have been:

### Form Location Is Non-Obvious
GHL forms are not found under a "Forms" menu. They are located under **Sites → Submissions**. The automation trigger is configured separately under the Automation section. This split makes it easy to overlook the connection between form and workflow.

### Spreadsheet Stored in the Wrong Location
The destination Google Sheet was saved under **Team → My Drive** rather than in the shared client drive. This made it nearly impossible to locate without already knowing where to look. Best practice is to store all client-facing assets in the shared drive so any team member can find and monitor them.

### No Proactive Monitoring
The failure was discovered because the client noticed missing data and called in. There was no automated test or alert in place to catch integration failures before they affect the client.

## Resolution

Mark reconnected the GHL–Google integration and verified that form submissions were flowing correctly to the spreadsheet. He also exported all historical form submissions and sent them to the client to ensure no leads were permanently lost during the outage.

## Required Follow-Up

- [ ] **Set up weekly GHL form test submissions with alerts** (@Mark Hope) — A scheduled test submission should run weekly; if the row does not appear in the sheet within a defined window, an alert fires. This catches the ~30-day Google integration expiry before the client notices.
- [ ] Move the destination Google Sheet from Team → My Drive to the appropriate shared client drive folder.
- [ ] Document the full automation path for Reynolds (form → GHL automation → Google Sheets) so any team member can diagnose future failures without a lengthy investigation.

## Broader Pattern

This incident is an example of a recurring risk class: **fragile third-party integrations with no failure alerting**. See also [[wiki/knowledge/automation-monitoring-gaps|Automation Monitoring Gaps]] for the general pattern and mitigation strategies.

The GoHighLevel–Google 30-day expiry issue is likely to affect any other clients using GHL → Google Sheets automations. All such integrations should be audited and added to the monitoring routine.

## Related

- [[wiki/clients/current/reynolds/index|Reynolds Client Overview]]
- [[wiki/knowledge/gohighlevel-google-integration-expiry|GoHighLevel Google Integration Expiry (Known Issue)]]
- [[wiki/meetings/2026-03-04-weekly-call-melissa|2026-03-04 Weekly Call with Melissa]]