GoHighLevel
Connect one GoHighLevel sub-account, choose the booking stage, and control what syncs
GoHighLevel
Connect GoHighLevel to keep contacts and opportunities current after every Aura booking and sales call.
Aura uses the pipelines and stages already in your selected sub-account. It does not change your workflows, automations, pipelines, or stages.
GoHighLevel is in early access while its Marketplace listing is under review. Open GoHighLevel from Aura's Integrations page and select Request early access. We will confirm a place before you connect.
Connect GoHighLevel
You must be an Aura organization admin.
- In Aura, go to Settings, then Integrations.
- Open GoHighLevel and select Connect GoHighLevel.
- Sign in and choose one sub-account.
- Approve access for Aura.
- Back in Aura, choose the pipeline and stage where a new booking belongs.
One GoHighLevel sub-account maps to one Aura organization. Aura stops the connection if it cannot identify exactly one sub-account.
Recommended setup
For most teams:
- Leave Leads and contacts on.
- Leave Booked calls on.
- Leave Won and lost outcomes on.
- Leave Contact updates from GoHighLevel on.
- Choose the pipeline and stage your team uses for newly booked calls.
GoHighLevel already provides standard Open, Won, and Lost opportunity statuses. Aura needs only the pipeline stage for a new booking. It does not need a Close-style mapping for every Aura lifecycle event.
What Aura writes
| Aura event | GoHighLevel behavior |
|---|---|
| Lead captured | Creates or matches a contact by email or phone |
| Genuine call booked | Creates one opportunity in your selected pipeline and booking stage |
| Call marked won | Updates the linked opportunity to won and adds the sale value |
| Call marked lost | Updates the linked opportunity to lost |
| Contact edited in GoHighLevel | Updates supported fields on the linked Aura lead when enabled |
Aura stores the GoHighLevel IDs it receives. A retry searches for the exact Aura call name, contact, and pipeline before creating an opportunity.
What Aura preserves
- Aura does not create, edit, or delete GoHighLevel workflows.
- Aura does not create or rename pipelines or stages.
- Aura updates only the opportunity linked to the Aura call.
- Aura does not delete GoHighLevel records.
- Disconnecting leaves all records already written to GoHighLevel in place.
Test environment
Aura uses a dedicated GoHighLevel test agency and sub-account for staging checks. The release check covers OAuth, agency and location tokens, token refresh, contact and opportunity writes, webhooks, and disconnect and reconnect.
Troubleshooting
Why do I see Request early access instead of Connect GoHighLevel?
Aura enables early access one organization at a time. Select Request early access and include your Aura organization name. We will confirm a place before enabling the private Marketplace installation.
Why is installation private during early access?
GoHighLevel allows a small number of invited customers to install an app before its public Marketplace review is complete. The connection and sync controls are the same ones planned for public release.
My pipeline or stage is missing
Select Check connection, then reload the page. Confirm that the pipeline belongs to the connected sub-account.
An opportunity was not created
Check that Booked calls is on and that a booking pipeline and stage are selected. Aura creates opportunities only for genuine bookings.
Aura connected the wrong sub-account
Disconnect and connect again. Select only the sub-account that belongs to this Aura organization. Aura will not guess when more than one account is approved.
The connection is invalid
Select Reconnect and approve GoHighLevel access again. Your Aura sync settings stay saved.
What happens when I disconnect?
Aura removes its stored credentials and stops all new sync activity. Existing contacts and opportunities stay in GoHighLevel. You can also uninstall Aura from the GoHighLevel Marketplace if you no longer want it listed in the sub-account.