TypeForm Lead Pipeline with Catch-Up Recovery

The Problem

A direct-response funding operator's highest-traffic TypeForm fired through a Zapier-managed chain that handled GoHighLevel contact creation, Hyros attribution, and Facebook conversion tracking together. TypeForm's partial-response event was unreliable, so leads who reached the booking page without submitting the partial got no qualification update, no Slack notification, and no opportunity moved to Call Booked. The workflow searched GoHighLevel for newly created contacts 35 seconds after creation, but the index needed 60 to 90 seconds, so the search returned zero results for leads that had just been created. Duplicate opportunities piled up across multiple form submissions because nothing checked the existing pipeline first.

The Build

I rebuilt the flow as a 40-node native n8n pipeline. A Switch at the top routes qualified, disqualified, and booking events down their own branches, each running Parse, GoHighLevel write, attribution call, and Slack notification in parallel. The catch-up mechanism is the centerpiece: when a booking event arrives, the workflow waits 90 seconds, looks up the contact, and checks whether the qualified-lead tag is present. If the tag is missing, the workflow knows TypeForm's partial event misfired and runs the full qualification path so no lead disappears. A Stage Guard inspects the existing opportunity's stage before moving it to Call Booked, and routes around closed-state opportunities by creating a fresh one instead, which keeps the closed opportunity's history intact. The Parse node matches TypeForm answers by substring of the question title rather than by field ID, so the workflow survives form edits.

The Outcome

Missed-partial leads now recover automatically through the catch-up path instead of vanishing. Duplicate opportunities stopped piling up because every qualified event checks the pipeline first. The Stage Guard keeps closed opportunities closed, so funded and disqualified deals stay where they belong. The Facebook Graph API version sits at v25.0 instead of the deprecated v19.0 the old flow was pinned to. The pipeline survives form edits because the Parse node matches TypeForm answers by question title, not by field ID.

Stack

n8nGoHighLevelTypeFormFacebook CAPIHyrosSlackJavaScript