Our Work — Drovin Solutions

GHL · Workflow Architecture

Multi-source lead routing with conditional opportunity creation

A real GHL workflow that tags inbound leads, branches based on source (Google Ads, dedicated landing page, OpenPhone, or none), then creates the opportunity in the correct pipeline. Built for a US cash-buyer real estate operator running multiple ad channels into one CRM.

GHL workflow with Add Tag, Condition node, and four branches each creating an opportunity

What's Inside

Trigger:Inbound lead via webhook, form or call tracking
Logic:4-way conditional branch on workflow source tag
Output:Source-specific opportunity in correct pipeline stage
Why it matters:Attribution stays clean even with 4+ active ad channels

GoHighLevel Workflow Builder Conditional Logic

GHL · Operations at Scale

Master pipeline managing 2,096 active opportunities

A live operational pipeline we manage for a client running paid social acquisition. Five-stage flow from Contacted needs sorting through Qualified Needs Booking, with full activity logging, opportunity values, and automated stage transitions.

GHL Master Pipeline showing 2,096 opportunities across five named stages with dollar values

System Stats

Volume:2,096 opportunities under management
Stages:5-stage qualification flow with $-value tracking
Source:Facebook lead-gen with automated GHL ingestion
Hygiene:Per-card activity, notes, scheduled tasks logged

GoHighLevel Pipeline Mgmt Facebook Ads Lead Routing

GHL · Form Automation

"Make an offer" form automation with execution logging

A multi-step form automation triggered by an inbound webhook: notify the team, search the CRM, branch on contact-found vs not-found, then add tags and create or update the contact record. Execution Log view confirms every step ran clean for this submission.

GHL workflow execution log showing inbound webhook, internal email, find contact and tag-add steps all executed

Flow Anatomy

Entry:Inbound webhook from offer form
Notify:Internal email with full webhook payload
Lookup:Find contact → branch (Found / Not Found)
Action:Tag with "offer submitted" + create/update contact

GoHighLevel Webhooks Conditional Branching Tag Management

n8n · Content Pipeline

Automated content pipeline → Google Sheets → LinkedIn

An internal n8n workflow ("Drovin Content — LinkedIn Publisher") we built and run daily. Ideas captured via Telegram bot pass through Whisper transcription and a Claude prompt into a Google Sheet, then auto-publish approved text posts to LinkedIn via Typefully. The execution panel shows real run history.

n8n executions panel showing successful and error runs, with Google Sheets trigger feeding If condition to JS code and HTTP request to Typefully

Stack

Trigger:Google Sheets row addition (approved post)
Logic:If-branch on visual vs text-only post
Transform:JS code node prepares Typefully payload
Publish:HTTP POST to Typefully API → LinkedIn

n8n Google Sheets Typefully API JavaScript

A2P 10DLC · Compliance

22/22 compliance checks passed across opt-in, privacy and ToS

A2P 10DLC SMS campaign registration is the single biggest reason agencies see SMS deliverability collapse — and the most under-served piece of the GHL build. This is a client compliance audit we ran: 8/8 opt-in form items, 7/7 privacy policy items, 7/7 terms-of-service items, all passed. Drovin's legal background is a hard differentiator here.

What We Reviewed

Opt-in:Business name, explicit consent, opt-out, frequency, message type
Privacy:Data collection, usage, SMS specifics, security, user rights
ToS:SMS use cases, opt-out instructions, liability terms
Outcome:Carrier-approved 10DLC campaign + clean deliverability

A2P 10DLC Compliance Audit Privacy Policy Twilio

GHL · AI Integration

GPT-5 Mini inside a GHL workflow for call-transcription processing

A GHL workflow ("Call transcriptions → Contact Notes") with GPT-5 Mini as a premium action. The model reads contact ID context, generates a unique call ID, and routes the result onward through anonymization and webhook steps. Native GHL premium GPT action — no Make/Zapier dependency.

GHL workflow node configuration showing GPT-5 Mini model with custom prompt referencing contact ID

Build Detail

Model:GPT-5 Mini via GHL premium action
Prompt:Custom, parameterized with {{contact.id}}
Pipeline:GPT → anonymization → webhook → Note action
Use case:Auto-summarize call transcripts into contact notes

GoHighLevel OpenAI GPT-5 Webhooks Prompt Engineering

Make.com · Multi-step Integration

Eventbrite → OpenAI Whisper → multi-branch GHL contact sync

A production Make.com scenario with 25+ modules. Eventbrite triggers a webhook on registration, data is normalized through a data store and tools, OpenAI processes audio inputs with Whisper, then a router splits to multiple GoHighLevel actions — creating contacts, updating fields, and syncing across multiple sub-accounts.

Make.com scenario with 25+ connected modules including Eventbrite, OpenAI Whisper, and multiple GoHighLevel actions

Architecture

Source:Eventbrite registration webhook
Storage:Make data store for state & deduplication
AI:OpenAI (Whisper, ChatGPT) for content processing
Output:Multiple GHL contact create/update actions via router

Make.com Eventbrite OpenAI Whisper GoHighLevel Data Stores

Process · Client Collaboration

Live system-design sessions on a shared whiteboard

How we actually scope an automation build with clients — not slide decks, but a working session on a shared whiteboard mapping the existing flow, the gaps, and the target architecture. Everything starts here, before a single workflow node is touched in GHL.

Live screen-share session with whiteboard sketching workflow architecture and a client task list

How We Work

Step 1:Live whiteboard discovery call (45–60 min)
Step 2:Map current flow + identify lead/data leaks
Step 3:Sketch target architecture before quoting
Step 4:Async build + Loom-recorded handoff

FigJam / Whiteboard Google Meet Loom Async-first

The actual systems, not the marketing copy.