Goddess Quiz Funnel
Botanical sacred feminine illustration

Implementation Dashboard

Building Your Goddess Quiz Funnel

A complete, step-by-step guide to connecting your Typeform score matrix to GoHighLevel โ€” without Zapier, without 64 workflows, and without custom code. Check off each step as you complete it; your progress is saved automatically.

0%

Complete

Funnel Architecture Overview

Here is how data flows through your funnel from quiz submission to personalized email delivery.

Quiz funnel data flow diagram
1๐Ÿ“‹

Typeform Calculation

Typeform calculates scores and determines the dominant and dormant goddesses using Custom Variables based on the user's answers.

2๐Ÿ”€

Dynamic Redirect

Upon submission, Typeform redirects the user to a GHL landing page, passing results as URL Parameters (e.g. ?dominant=Athena&dormant=Aphrodite).

3๐ŸŒฟ

Dynamic Landing Page

GoHighLevel reads the URL parameters and dynamically displays the correct dominant goddess result, along with your upsell offers.

4โšก

Webhook Data Transfer

Simultaneously, Typeform sends the lead's contact information and quiz results directly to GoHighLevel via an Inbound Webhook.

5โš™๏ธ

GHL Workflow Automation

GoHighLevel receives the webhook data, creates/updates the contact, saves their goddesses into Custom Fields, and triggers an email Workflow.

6โœ‰๏ธ

Email Delivery

The Workflow uses an If/Else branch to send a personalized email focusing on their dormant goddess, while dynamically inserting the dominant goddess name.

I๐Ÿ“‹

Phase 1: Preparing Typeform

Configure Custom Variables & Redirect URL

0/2
steps done
Step 1

Ensure you have Custom Variables in Typeform that store the final text value of the dominant and dormant goddesses.

  1. 1In Typeform, go to the Workflow tab and click the (x) Variables icon.
  2. 2Click + Add custom variable and choose Text from the drop-down menu.
  3. 3Create a variable named dominant_goddess (leave base value blank).
  4. 4Create a second variable named dormant_goddess (leave base value blank).
  5. 5Note: Only lowercase letters, numbers, and underscores are accepted in variable names.
โœฆ Pro Tip: If your matrix currently outputs only numerical scores, you will need to use Typeform's Logic > Branching and calculations to assign the final string names (e.g. "Athena", "Aphrodite") to these two variables. Under each branch, choose Replace as the action and type the goddess name as the new value.
Step 2

Instead of using Typeform's default End Screens, redirect users directly to your GoHighLevel funnel page with the results embedded in the URL.

  1. 1In Typeform, go to the Endings panel and click + to add a Redirect to URL ending.
  2. 2Enter your GoHighLevel landing page URL as the base.
  3. 3Use Typeform's Recall information feature (type the @ symbol) to insert your variables into the URL.
  4. 4Your redirect URL should look exactly like the example below.
  5. 5When you type @dominant_goddess, Typeform creates a dynamic bubble representing that variable โ€” it will be replaced with the actual goddess name on submission.

Redirect URL Template

https://yourdomain.com/quiz-results?dominant=@dominant_goddess&dormant=@dormant_goddess
II๐ŸŒฟ

Phase 2: Building the Dynamic Landing Page

GoHighLevel Dynamic Text via URL Parameters

0/2
steps done
Step 1

Build your main results page in GoHighLevel. This page will reveal the dominant goddess, the eBook upgrade offer, and the Sacred Leadership Initiation upsell ($111/month).

  1. 1In GoHighLevel, go to Sites > Funnels and create a new funnel called 'Goddess Quiz Results'.
  2. 2Add a new page step and design your results page with sections for: the goddess reveal, the eBook upsell, and the Sacred Leadership Initiation offer.
  3. 3Design the page to look beautiful even before the dynamic content loads โ€” use placeholder text like 'Your Goddess' that will be replaced.
โœฆ Pro Tip: If you have entirely different images or long text blocks for each of the 8 dominant goddesses, consider creating 8 separate result pages in GHL (one per goddess) and using Typeform's Logic to redirect to the specific URL. This avoids messy URL parameter logic for rich content.
Step 2

Anywhere on the page where you want to display the dominant goddess name, use GHL's native URL parameter syntax. GoHighLevel will automatically read the URL and replace the placeholder with the actual goddess name.

  1. 1In the GHL page builder, click on any text element where you want the goddess name to appear.
  2. 2Type the parameter placeholder exactly as shown below (double curly braces).
  3. 3Because your Typeform redirected the user to a URL ending in ?dominant=Athena, GHL will automatically replace {{dominant}} with 'Athena' on the live page.
  4. 4You can use the same approach for the dormant goddess: {{dormant}}.

GHL URL Parameter Syntax

{{dominant}}

// Example usage in your page copy:
"Welcome, sister. Your dominant goddess energy is {{dominant}}."
"Your dormant goddess โ€” the one calling to be awakened โ€” is {{dormant}}."
IIIโšก

Phase 3: Connecting Typeform to GoHighLevel

Native Webhook Integration โ€” No Zapier Required

0/4
steps done
Step 1

Before sending data, GHL needs a place to store the goddess results on each contact record.

  1. 1In GHL, go to Settings > Custom Fields.
  2. 2Click Add Field and select Single Line Text as the field type.
  3. 3Create a field named Dominant Goddess.
  4. 4Create a second field named Dormant Goddess.
  5. 5These fields will now appear on every contact record and can be used in email merge tags.
Step 2

Create a new Workflow in GoHighLevel that is triggered by an incoming webhook from Typeform.

  1. 1Go to Automation > Workflows and click + Create Workflow.
  2. 2Click Add New Trigger and select Inbound Webhook.
  3. 3Note: The Inbound Webhook is a premium trigger in GoHighLevel โ€” ensure your plan includes it.
  4. 4GHL will generate a unique Webhook URL. Copy this URL โ€” you will need it in the next step.
  5. 5Save the workflow trigger.
โš  Note: The Inbound Webhook trigger requires a GoHighLevel plan that includes premium workflow triggers. Check your plan level if you do not see this option.
Step 3

Paste the GHL webhook URL into Typeform so that every quiz submission is automatically sent to your workflow.

  1. 1In Typeform, go to Connect > Webhooks and click Add a webhook.
  2. 2Paste the GHL Webhook URL you copied in the previous step.
  3. 3Enable the webhook and save.
  4. 4CRUCIAL: Fill out your Typeform quiz yourself with test data and submit it. This pushes a test payload of data to the webhook so GHL can see the data structure.
โœฆ Pro Tip: Always test with real data before mapping fields. GHL needs to receive at least one test submission to show you the available data fields for mapping.
Step 4

Back in your GHL Workflow, map the incoming Typeform data to the correct GHL contact fields, including your new Custom Fields.

  1. 1In your GHL Workflow, click on the Inbound Webhook trigger and look for the test data you just sent.
  2. 2Add your first Workflow Action: Create/Update Contact.
  3. 3Map the incoming data: Typeform email field โ†’ GHL Email field, Name โ†’ Name, etc.
  4. 4Scroll down to Custom Fields in the action menu.
  5. 5Map the Typeform dominant_goddess variable โ†’ your GHL 'Dominant Goddess' custom field.
  6. 6Map the Typeform dormant_goddess variable โ†’ your GHL 'Dormant Goddess' custom field.
IVโœ‰๏ธ

Phase 4: The Email Automation Workflow

8 Branches ร— 1 Merge Tag = All 64 Combinations

0/2
steps done
Step 1

In the same workflow you created in Phase III (after the Create/Update Contact action), add an If/Else action. This splits the workflow based on the dormant goddess โ€” you only need 8 branches, not 64.

  1. 1In your GHL Workflow, after the Create/Update Contact action, click + Add Action.
  2. 2Select If/Else from the action list.
  3. 3Name the action 'Check Dormant Goddess'.
  4. 4Branch 1: Condition โ†’ Contact Details โ†’ Dormant Goddess โ†’ Is โ†’ 'Persephone'
  5. 5Branch 2: Condition โ†’ Contact Details โ†’ Dormant Goddess โ†’ Is โ†’ 'Hera'
  6. 6Continue adding branches until you have one for each of the 8 possible dormant goddesses.
  7. 7The 'All Other Cases' branch at the bottom acts as a safety net.
โœฆ Pro Tip: You do NOT need 64 workflows or 64 emails. You only need 8 branches (one per dormant goddess). The dominant goddess is handled dynamically via a merge tag in every email.
Step 2

Under each of the 8 branches, add a Send Email action. Each email is tailored to the dormant goddess but uses a merge tag to dynamically insert the dominant goddess name.

  1. 1Under each If/Else branch, click + Add Action and select Send Email.
  2. 2Write an email focused on that branch's dormant goddess.
  3. 3To mention the dominant goddess dynamically, use the GHL Custom Value merge tag shown below.
  4. 4Because GHL saved their dominant goddess to their contact profile, the merge tag will automatically populate with the correct goddess name for each person.
  5. 5This single workflow handles all 64 possible dominant/dormant combinations.

Dynamic Email Template

// GHL merge tag for the dominant goddess:
{{contact.dominant_goddess}}

// Example email copy for the 'Persephone' branch:
"Welcome, sister. As you saw on the previous page,
your dominant energy is {{contact.dominant_goddess}}.

But what we didn't discuss on that page is your
dormant energy: Persephone.

Working with Persephone is crucial to your initiation
because..."

Key Insights

The four principles that make this funnel work without custom code or middleware.

๐Ÿšซ

No Zapier Required

GoHighLevel's native Inbound Webhook trigger handles the entire Typeform-to-GHL data transfer without any third-party middleware.

๐Ÿ”ข

8 Branches, Not 64

The If/Else workflow only needs 8 branches (one per dormant goddess). The dominant goddess is inserted dynamically via a merge tag, covering all 64 combinations automatically.

๐Ÿ“

Custom Fields, Not Tags

Tags are for internal segmentation. Custom Fields (Single Line Text) are what allow GHL to store and dynamically display the goddess names in emails and on pages.

๐Ÿ”—

URL Parameters = Dynamic Pages

GHL natively reads URL parameters and replaces {{placeholders}} on your landing page. No custom code needed โ€” just append ?dominant=Athena to your redirect URL.

Is This Funnel Possible?

Yes, entirely. The full funnel โ€” from Typeform quiz to personalized email โ€” is achievable using native features of both platforms. No Zapier, no custom code, no 64 separate workflows. Any experienced GoHighLevel architect will look at this blueprint and know exactly how to build it in a few hours.

On the contractor situation: the architecture described (custom fields passed to a dynamic landing page) is correct. The issue is likely that Tags were used instead of Custom Variables, which is why data isn't flowing correctly. The fix is in Typeform's logic, not in any custom code.

Funnel Pages โ€” Live Previews

All five funnel pages are built and ready. Open each to review the copy and design before handing off to your GHL tech team.

References

Official documentation supporting every step in this guide.