Setting Up Products With “Go High Level”

Overview

In this article, we’ll go over how to connect Go High Level to your VT system using Zapier.

Connect Stripe

Once you’ve logged into Go High Level, you’ll need to connect the Stripe account. Click on the “Launchpad” button location in the left side bar, then click the connect button in the Stripe section and choose the account to connect to. Once you do this, the connect button will turn into a green circle with check mark, indicating that the connection was made successfully.

Setting up Trigger (Webhook) In Go High Level

Triggers are basically webhooks in Go High Level, to set them up, click on the “Trigger” button in the left sidebar, then click on “Add Trigger”.

Step 1 – Trigger and Filter: For the trigger, choose “Order Form Submission”. Next add a filter, it should be set to “Submission Type” and “Sale”

Step 2 – Action: Click “Add Action” on the right side of the page, but don’t choose anything yet, then save the trigger. We’ll add the action, later on when setting up Zapier.

The image above shows what the GHL trigger should look like after you paste Zapier’s webhook endpoint in.

Create Products

Subscription Based Products

If the product is subscription based, then you’ll need to create the product in Stripe first. After you created the product in Stripe head back over to Go High Level and navigate to the funnel, then click the “products” hyperlink, then click “Add Product”. From there you’ll have the ability to either import products or choose products that were previously imported from the drop down

One Time Products

If you’re creating a one time product, this will need to be done from within Go High Level. Navigate to the funnel and click the “Products” hyperlink. If you haven’t created the product yet, click the “Here” hyperlink under the product drop down and created the one time product. Once you’ve done this, go back to the “Products” section then click “Add Product” and choose the product you wish to add to the funnel.

Setting up Zappier

Zapier is an integration tool that you can use to grab data from GHL customers. When a customers purchases from you GHL funnel, Zapier can use that data to create the user in your VT system. Learn more or sign up for Zapier Here. In this article, we’ll go over the following steps involved with setting up Zapier with GHL

Step 1: Trigger – (Webhook / Catch hook)
Step 2: Action – (Text Formatter)
Step 3: Paths (For initial product, bump product, and any upsell products)

Step1: Trigger (webhook / Catch hook)

When setting up the trigger, choose “Webhooks by Zapier”, then choose “Catch hook”.

On the next step, Zapier will give you a webhook URL that you’ll need to paste into GHL. Once you’ve copied the URL, head back over to GHL and click “Triggers” in the sidebar, then click on the trigger that you set up in the previous step and set the Action to “Execute Web hook”.
A “Web hook URL” field will appear below, this is where you will place the Zapier URL that you copied.

Before you can test the trigger in Zapier, you’ll need some test data to work with. Go back to the funnel and run through a test transaction. You can either use a live test card and refund the card afterwards, or you can put the funnel in test mode and use Stripe’s test card. We’re going to be putting the funnel into test mode and use the test card below

cc#: 4242424242424242
exp: any time in the future
cvv: code can be anything

After you’ve run the test transaction, go back over to Zapier and click “Test Trigger” to see the test data.

Step 2: Text Formatter

The next step is to set up a formatter. Since the form in GHL only has one field for the full name, there will most likely be some customers that only enter their first name. The formatter will check to see if there is a last name present, if there is then the formatter will leave the last name field as is, but if there isn’t, then the formatter that we will use will put in a default value.

Choose the “Format” option, then choose “Text” as the action event.

When you get to the Set up action, the Transform option should be set to “Default Value”. The Input value should be the “Last Name” filed from the webhook payload and the default value should be hard coded to “none”.

Step 3: Path (for initial product, bump product and upsells)

The last step is to set up “Paths”, which handle what happens when products are purchased. Add another action step and choose “Path”.

Path A – Initial Purchase Without Bump Product(Create User)

If you’re selling a bump product along with the initial product, the setup will be a little different than just selling one product by itself, click here to skip to that setup.

First, Set the name of the first path, this can either be the name of the product or something like “Initial Purchase (Create User)”.

Next, you’ll need to set the condition in the “Rules setup & testing” section. You’ll want to only allow the zap to continue if the “Order Product Id” exactly matches the “INTERNAL PRODUCT ID” (hard coded value) within Go High Level, you can get the Internal Product Id from the products section

Find the user in LSVT

Next, you’ll need to make sure the user doesn’t already exist in the system. Add a third action and choose “LightSpeed VT”, then choose “Find user” as the action event. After that, you’ll need to connect your system to zapier if it’s not already connected, you can find the zapier credentials for your system in the API section of webservices. Next, you’ll choose to search for the user by username, which will be set to the email address, after that set the “Should this step be considered a “success” when nothing is found?” option to yes.

Set up a filter

The next step is to set up a filter, which will only allow the zap to continue if the “Find User in LightSpeed VT” returned “False”

Create User in your VT system

For the action, choose LightSpeed VT, then choose, create user for the action event. Go through the steps involved with choosing or connecting an account. In the setup process, set the following fields

Username: catch hook email
Password: Temporary password, something like {Systemname}PW123
First name: catch hook first name
Last name: text formatter last name
Email: catch hook email
Access Level: system access level
Location Id: system location that users should be placed in
Content Role: content role for initial product
Stripe Order id: For one time payments – catch hook “Order Order Id”
For subscriptions – catch hook “Order Metadata Subscription”

Path A – Initial Purchase with Bump Product (Create User)

If you’re offering a bump product, the path will be similar to the initial product (Path A) setup, but the “Rules setup & testing” filter will be set up differently.

Instead of setting it up so that the “Order Product Id” exactly matches “INTERNAL PRODUCT ID” (hard coded value), you’ll need to set it up so that the “Order Metadata Lines Data Metadata Internal Funnel Product ID” contains the “INTERNAL PRODUCT ID” (hard coded value). Since there are two products being sold, the payload coming over from Go High Level will have two product ids. The “Order Metadata Lines Data Metadata Internal Funnel Product ID” will contain both the initial product’s id and the bump product’s id.

Find the user in LSVT

Next, we need to make sure the user doesn’t already exist in the system, there’s a nifty tool for this. Add a third action and choose “LightSpeed VT”, then choose “Find user” as the action event. After that, you’ll need to connect the client’s system to zapier, if it’s not already connected, you can find the system’s zapier credentials in the API section of webservices. Next, you’ll choose to search for the user by username (which will be set to the email address) and set the “Should this step be considered a “success” when nothing is found?” option to yes.

Filter

Create User in your VT system

For the action, choose LightSpeed VT, then choose, create user for the action event. Go through the steps involved with choosing or connecting an account. In the setup process, set the following fields

Username: catch hook “email”
Password: Temporary password, something like {Systemname}PW123
First name: catch hook “first name”
Last name: text formatter “last name”
Email: catch hook “email”
Access Level: system access level
Location Id: system location that users should be placed in
Content Role: content role for initial product
Stripe Order id: For one time payments – catch hook “Order Order Id”
For subscriptions – catch hook “Order Metadata Subscription”

Path B – Initial Purchase (update user)

Next, we’ll need to set up a path in case a user that already exists purchases. The steps involved will be similar to the steps in Path A, the only difference is the “Filter by Zapier” will only continue if the “Find User in LightSpeedVT” step returns “True”, meaning that the user already exists in the system. After that you’ll choose to “Update User” instead of “Create User”

Path C – Upsell Products

Since Path A will be responsible for creating the user, the steps involved with setting up paths for upsells will pretty much be the same as Path B (update user). You’ll set up the path’s first filter to only continue if the “Order Product ID” matches the “Internal Product ID” of the upsell product in Go High Level.

Testing The Zap

When testing the the funnel and zap, make sure you run through different scenarios. For example, run through a test and input a first and last name into the name field, then run another test with only one name in the name field to see what happens. If there is an initial product and a bump product, run through a test an only purchase the initial product, then run through another test and purchase the initial and bump product to make sure everything runs without issues.