Disclosure: some links in this post are affiliate links. If you sign up through them I may earn a commission, at no extra cost to you.
Here’s the direct answer: you build a GoHighLevel form that fires a webhook into Zapier, Zapier creates a client folder in Google Drive and shares it with the client, then Zapier sends the form answers to Google Gemini, which writes a custom offer, social posts, and a 30-day plan — and Zapier drops each one into its own Google Doc inside that same folder. No developer needed. Here’s the actual build, piece by piece, in this GoHighLevel tutorial.
Why bother automating onboarding at all?
Quick answer: most onboarding forms just sit in a pipeline unused, but in this setup every intake answer — business type, current offer, goal, business description — feeds an AI that hands the client a real starting point: an improved offer, ready-to-post social content, and a 30-day plan, all within minutes of submitting the form.
Here’s the thing — most people onboard a new client with a generic welcome email and a form that just sits in a pipeline. Nobody actually uses the answers. In this GoHighLevel tutorial, every question on the intake form gets reused later — business type, current offer, goal, a description of the business — all of it feeds an AI that hands the client a real starting point: an improved offer, ready-to-post social content, and a 30-day plan. The client gets something useful in minutes instead of waiting on you to get to it.
This is the same worldview I keep coming back to: a business doesn’t need 30 disconnected tools. It needs a handful that actually talk to each other. GoHighLevel captures the form. Zapier moves the information. Gemini does the writing. Google Drive stores it. That’s the whole ecosystem.
Step 1: Build the onboarding form inside GoHighLevel
Start in Sites → Forms → Builder. Create a folder first — naming it something like “00 Onboarding” keeps every piece of this project (the form, the automation, the Zap) labeled consistently, which matters once you’ve got a dozen automations running.
Inside the folder, build the form from scratch: first name and last name (required), email, and then a website field marked optional — “because some people might not have a website, because they’re just beginning, and they’re beginning with you.” After that, pull in the questions that actually matter for what comes later: what type of business they’re in, what they currently offer, what their goal is for using the software, and what their current offer looks like. Every one of these answers becomes a variable Gemini will use to write personalized content, so don’t skip them.
A naming habit worth stealing
Whatever you name the folder, name the form and the automation to match. It sounds small, but when you’re juggling forms, workflows, and Zaps across a CRM, matching names is the difference between finding something in five seconds and hunting for ten minutes.
Step 2: Trigger a webhook when the form is submitted
Inside GoHighLevel, build an automation that triggers on Form Submitted, pointing at the onboarding form. The action is a webhook — think of it as an information tunnel, sending everything the client typed into the form over to Zapier. You’ll grab the actual webhook URL from Zapier’s side and paste it back into GoHighLevel’s post field. Nothing fires until both ends are connected, so this step has to happen before you can test anything downstream.
Step 3: Catch the webhook and find (or create) a Google Drive folder
In Zapier, the trigger is “Catch Hook” — it automatically formats whatever comes in, so you’re not parsing raw data by hand. Submit a test entry through your form to give Zapier something real to work with, then test the trigger.
The next step is Google Drive → Find a Folder. Name the folder using the client’s full name plus their email — a combination that’s guaranteed to be unique, since no two customers are going to have the same name and the same email. Set the parent folder to a client folder you’ve already created in your Drive (call it something simple, like “Client Folder”), and set the fallback behavior to create the folder if no exact match is found. This step also protects you against duplicate entries from repeat customers.
Right after that, add a second Google Drive step — Add File Sharing Preferences — using the folder ID from the step before, sharing role set to Editor, and the client’s email pulled straight from the form. That’s how the client actually gets access to their own folder.
Step 4: Set up Google Gemini through Google AI Studio
This is the part of the GoHighLevel tutorial that trips people up, and it’s worth naming honestly upfront.
The one real gotcha
Getting a working Gemini API key means going through Google AI Studio, creating a Google Cloud project, and turning on billing — and billing approval can take a day or two to clear. As Nuno puts it plainly:
“I’m going to save you the heartache because it does take one, two days to get this ready. So you might want to do this first.”
Do this step before you build anything else. Google gives a free trial with credit toward usage, but the free tier alone will hit its quota fast once Zapier starts calling it repeatedly, so plan on linking a billing account.
Writing the prompt without being a prompt engineer
You don’t need to hand-craft this. Copy your form’s questions, paste them into a Gemini chat, and ask it to design three AI agents — an offer agent, a social media agent, and a 30-day planning agent — each producing one final response instead of a back-and-forth conversation. That last instruction matters: since Zapier calls Gemini once and expects one answer back, you have to tell it flat out not to treat this like a conversation.
Step 5: Map form fields into the Gemini prompt inside Zapier
Add a Google AI Studio step in Zapier, choose “Send Prompt,” pick your model (Gemini 2.5 or Gemini 3, depending what’s available when you build this), and paste in the system instructions Gemini generated. Then swap every placeholder in the user prompt for the actual form fields — client name, business type, business context, current offer, and goal — using Zapier’s field picker so it pulls live data from each submission.
One practical note from the build: asking for too much output (five posts, long plans, multiple agents in one call) can cause the request to time out. Dropping the ask down — three posts instead of five, for example — fixed it. Keep each agent’s job narrow rather than piling every instruction into one prompt; overloaded prompts produce muddier results anyway.
Step 6: Turn each Gemini response into a Google Doc in the client’s folder
Add a Google Docs step — Create Document from Text — for each of the three outputs. Name each document using the client’s email plus a label (“offer ideas,” “social posts,” “30-day plan”), and set the destination folder to the client’s Drive folder created back in Step 3. Repeat this for all three AI agents, so the client ends up with three documents sitting in one folder, shared and ready the moment they submit the form.
Once the first document works, you can copy that whole action, paste it, and just swap the prompt and document name for the next agent — much faster than building each one from scratch.
Frequently asked questions
Do I need a paid Zapier plan for this?
Yes — this build needs Zapier’s paid tier, since webhooks and this many chained actions aren’t available on the free plan.
Why use Google Gemini instead of ChatGPT?
Gemini was the strongest option at the time of this build, with access to Google AI Studio’s models and image tools bundled into the same API key. The specific “best” model changes constantly, so treat this as a template you can point at whichever AI you prefer.
What happens if a client doesn’t have a website?
The website field on the form is optional. Everything downstream — the folder creation, the Gemini prompts, the generated documents — still works fine without it.
Can this same setup work for existing clients, not just new signups?
Yes. The Find a Folder step checks for an existing folder before creating a new one, so it also protects against duplicate folders if a returning client fills the form out again.
If you want the full step-by-step build with the exact form fields, folder structure, and prompts laid out start to finish, that’s exactly what the GoHighLevel Masterclass walks through. And if you’re new here, what Automated Marketer is is worth reading first — it explains the free training approach behind everything on this site, including the FAQ for common GoHighLevel questions.