Close Won → Onboarding Workflow Architecture
Design Principle
GHL handles the trigger and simple native actions. N8N handles all complex logic.
GHL Side (Minimal)
- Trigger: Pipeline stage changed to "Close Won" in Sales Pipeline
- Action: Remove from all other workflows (native GHL action)
- Action: Send webhook to N8N
N8N Side (Heavy Lifting)
- Log webhook — Extract contact data from GHL webhook payload
- Create SaaS client — Insert into Supabase
clientstable - Generate magic link — Create unique onboarding URL for the client
- Save token — Store authentication token in Supabase
- Cancel sales enrollments — Disenroll from all sales-related N8N workflows
- Create onboarding opportunity — Move to onboarding pipeline stage
- Send welcome SMS: "Hey {first_name}, welcome to Iron Automations! We're getting everything set up for you. Here's your onboarding form — takes about 5 minutes. {magic_link}"
- Send welcome email — Same content with more detail
- Post notification — Send to Mattermost notifications channel (NOT SMS replies channel)
Key Decisions
- No inbound webhooks to GHL — Premium feature, never use it. Always send data OUT of GHL to N8N.
- No custom webhook actions — Also premium. Off the table.
- Tags: Only use if absolutely necessary for triggering other automations. Pipeline stage changes are preferred.
- Onboarding form reminders: Should be a SEPARATE workflow, not bundled into this one.
Magic Link Onboarding Form Flow
The magic link leads to a mobile-optimized multi-step form:
- Loom video walkthrough explaining each question
- Services offered (creates individual pages on website)
- Service area / cities served (creates location pages)
- Google Business Profile link
- Facebook page link
- Logo upload (or request generation)
- Brand colors
- Photos (5-10 of job sites, team, equipment)
- Business details (legal name, address, phone, email)
- Domain name (existing or request new)
Form submissions feed into Iron Funnels for automated site/funnel generation.