Connect Priceguide to GoHighLevel Directly (Native Integration, No Zapier)

What this does

Before you start

You need four things. The third one is the step people miss.

#	Requirement	Notes
1	A Priceguide account with at least one published estimator	Draft estimators won’t fire events
2	A GoHighLevel sub-account	The app installs at sub-account level
3	LC Premium Triggers & Actions enabled for that sub-account	See the warning below
4	Admin access to the GHL agency or sub-account	Needed to install marketplace apps

 

⚠️ Enable Premium Triggers first

GoHighLevel requires Workflow LC Premium Triggers & Actions to be enabled on a sub-account before any marketplace app trigger will run — Priceguide’s included.

If it isn’t enabled, everything below will still look correct. The app installs, the workflow saves, the trigger sits on the canvas. It simply never fires, and there is no error message telling you why.

Turn it on in your agency settings, for the sub-account you’re connecting, before you build anything. Agencies can also rebill this to their sub-accounts.

Steps on connecting Priceguide to GoHighLevel

Step 1 — Find the app

Inside the sub-account you want leads to land in, open App Marketplace from the left-hand menu, and search for priceguide.

Click the Priceguide card.

You should see:
• App Category — Advertising, Lead Generation
• Pricing — Free
• Who can install — Agency and Sub-Account
• Developer — Priceguide

Click Install.

Step 2 — Choose the sub-account and approve

Pick the sub-account that should receive the leads, then click Continue.

GoHighLevel now shows what the app can access.

What Priceguide asks for:

Permission	Access	Why
Workflows	Read	To register the Estimate Created trigger
Locations	Read	To identify which sub-account to send leads to
Users	Read	To identify the installing user
Charges	Read + Write	Required by GoHighLevel for per-execution billing (see Costs)
Marketplace Installer Details	Read	Standard install metadata

The Custom Triggers section lists a single trigger — Estimate Created. That’s the whole integration surface.

Click Allow & Install.

Step 3 — Sign in to Priceguide

You’ll be redirected to Priceguide to sign in. This is the step that tells Priceguide which account’s estimates belong to this GHL sub-account.

• If you’re already signed in to Priceguide in that browser, this passes through instantly and you may not see a login screen at all.
• If you’re not, you’ll get the standard Priceguide login. Sign in with the account that owns the estimator.

Either way you land here:

🔑 This login decides the routing

There is no estimator picker during install. The Priceguide account you log in with is the account bound to this GHL sub-account.

Log in with the right account the first time. If you manage several businesses in Priceguide, see Multiple estimators below.

Step 4 — Build the workflow

Go to Automation → Workflows and click Create workflow → Start from Scratch.

On the blank canvas, click Add New Trigger, and type priceguide into the search box.

You must type “priceguide” to find it. The trigger is listed under the app name, not under a category, so browsing the trigger list won’t surface it.

Under Installed apps → Priceguide, select Estimate Created.

The config panel has two things:

• Workflow Trigger Name — leave as Estimate Created, or rename it
• Add filters — optional; see below

Click Save trigger. Your canvas now looks like this:

Multiple estimators

If your Priceguide account has more than one estimator, every estimator will fire into this workflow by default.

To restrict it to one, click Add filters and filter on Estimator ID. Build one workflow per estimator, each filtered to its own ID.

You can find an estimator’s ID in your Priceguide dashboard.

Step 5 — Create the contact

Click the + below the trigger and add a Create/Update Contact action.

For each field, use the value picker to pull the matching value from the estimate:

GHL contact field	Value from the estimate
First / Last Name	Lead’s name
Email	Lead’s email
Phone	Lead’s phone
Postal Code	ZIP entered in the estimator
Custom field (create one)	URL of the estimate results page

Save the results URL. It’s the single most useful field in the payload — it opens the exact estimate the customer saw, with every answer and the price range. Create a custom field for it (e.g. Priceguide Results URL) and map it here. Your team can then open a lead’s full job context in one click.

Add whatever else you want after this — assign an owner, send an SMS, add a tag, start a nurture sequence. That’s ordinary GHL workflow building from here.

Field labels in the picker are provisional in this draft. Confirm the exact wording against a live workflow before this guide is published — see Open items.

Step 6 — Publish

Toggle the workflow from Draft to Publish in the top right.

A workflow left in Draft will not run. This is the second most common reason a working setup appears to do nothing.

Step 7 — Test it

1. Open your estimator on your live site.
2. Complete it end to end with a real email address you control.
3. In GHL, go to Contacts and confirm the contact appears.
4. Open the workflow’s Execution logs tab to see the run.

If the contact appears with the right details, you’re done.

Costs

The Priceguide app is free. GoHighLevel charges a platform fee of $0.01 per trigger execution — roughly one cent per completed estimate.

To be clear about who charges what:

• • This is GoHighLevel’s own LC Premium Triggers & Actions fee
• • It applies to every third-party marketplace trigger on the platform, not just Priceguide’s
• • It is billed by GoHighLevel to your GHL account. Priceguide receives none of it.

We have asked GoHighLevel to waive this fee for the Priceguide app under their premium action/trigger charge waiver programme. This guide will be updated if and when that’s granted.

At 500 estimates a month, the fee is $5.

Troubleshooting

Nothing arrives in GHL at all

1. Is LC Premium Triggers & Actions enabled for this sub-account? This is the most common cause. Without it the trigger never runs and reports no error.
   
2. Is the workflow Published, not Draft?
3. Is the estimator published in Priceguide?
4. Check the workflow’s Execution logs — if there are no entries, the trigger isn’t firing; if there are entries but no contact, the problem is in the Create Contact action.

Leads from the wrong business are arriving

The install is bound to the Priceguide account you signed in with. If that account holds several estimators, all of them fire here. Add an Estimator ID filter to the trigger (Step 4).

I can’t find the trigger when building the workflow

Type priceguide into the trigger search. It’s listed under the app name and won’t appear by browsing categories.

I signed in with the wrong Priceguide account

Uninstall the app from the sub-account and reinstall it, signing in with the correct account.

Open items for internal review

Remove this section before sending to customers.

• • Field labels in Step 5 are provisional. Capture the real value-picker options from a live Create/Update Contact action and correct the table. Also confirm whether richer fields (service type, price range, individual answers) are exposed — if they are, they deserve their own table, since “the lead arrives with full job context” is the core pitch.

• • Estimator ID filter — confirm the exact filter field name, and document where a franchisee finds their estimator ID in the Priceguide dashboard.

• • End-to-end test not yet completed. Steps 1–4 are verified against a live install in the PriceguideTest sandbox (sub-account krcvaFnd2qnvRcAiYDeb). Steps 5–7 are written from the platform’s documented behaviour and need one real estimate pushed through before publication.

• • Screenshots are from a sandbox agency account. Re-shoot in a white-labelled account if this ships to franchise brands.

• • ai/integrations-tracking still tells customers to connect GoHighLevel via Zapier and doesn’t mention the native app. Needs updating alongside this guide.

• • App listing — the Resources → Website field renders blank on the install confirmation screen. Minor polish.

• • Agency-level install is possible but not covered here. If agencies need it, it warrants its own short section, including rebilling the premium-trigger fee to sub-accounts.