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.

Connect GoHighLevel

You must be an Aura organization admin.

1. In Aura, go to Settings, then Integrations.
2. Open GoHighLevel and select Connect GoHighLevel.
3. Sign in and choose one sub-account.
4. Approve access for Aura.
5. Back in Aura, choose your pipeline and map the Opportunities columns you want Aura to manage.

One GoHighLevel sub-account maps to one Aura organization. Aura stops the connection if it cannot identify exactly one sub-account.

White-label GoHighLevel

If your agency runs GoHighLevel under its own name and web address, sometimes shown as LeadConnector, connect the same way. Connect GoHighLevel opens GoHighLevel's own sign-in page. Sign in with the email and password you use for your agency's app, then choose your sub-account.

More than one business

Each business needs its own Aura organization, and each organization connects its own sub-account. An agency can install Aura on as many sub-accounts as it needs.

One sub-account can only be connected to one Aura organization at a time. If another organization already uses it, Aura stops and tells you.

Installing Aura from GoHighLevel

You can also install Aura from GoHighLevel's app list or from an install link. GoHighLevel then sends you to Aura without saying which Aura organization the install is for. If you see Finish connecting GoHighLevel, select Connect GoHighLevel and choose your sub-account. That links it.

GoHighLevel only lists sub-accounts that do not have Aura yet. If yours is missing, see GoHighLevel doesn't list my sub-account.

Installing Aura again after removing it

If you remove Aura from a sub-account in GoHighLevel, Aura keeps your settings and shows Aura was removed from your GoHighLevel account. GoHighLevel can take about 30 minutes before it lists that sub-account again. Then install Aura on it again from GoHighLevel, and Aura links it back to the same organization with your settings in place. Selecting Connect GoHighLevel in Aura works too.

Pipeline mapping

Every Opportunities column can be mapped: Interested, Disqualified, Qualified, Booked Call, Confirmed Call, Declined, Cancelled, Completed, Bad Fit, No Show, Follow-up Required, Lost and Won.

Choose a stage for each column Aura should manage. You can send several columns to the same stage, or leave any column unmapped. Save the mapping to apply your choices. Clearing a row stops stage changes from that source after you save. A save applies to future transitions and does not move historical records.

Aura checks the current Opportunities column when a queued update runs. An older outcome does not move a lead out of a newer booking. A booking can change column when its start time passes, and attendance can move it to Completed before the final outcome is recorded.

Aura can continue the same linked opportunity across later bookings for the same lead and pipeline. Each booking keeps its link, and the lead's current Opportunities column controls the next mapped stage change.

GoHighLevel tracks opportunity status separately from stage. A new opportunity starts open unless its mapped source is Won or Lost. Moving an existing opportunity to a nonterminal stage preserves its status, including a previously won or lost status. A mapped Won or Lost source updates that status; an unmapped source changes neither. No Show, Bad Fit, Declined and Cancelled do not mark an opportunity abandoned.

GoHighLevel's Allow Multiple Opportunities per Contact setting controls whether new duplicate cards are permitted in the same pipeline. Aura continues its verified linked opportunity and does not change that setting.

In Sync controls, Pipeline stages has three choices:

• Each switch decides: Lead capture, Call booking and Won / lost outcome each move their own columns.
• Move the stages I mapped: every column you mapped moves.
• Don't move any stages: no stage moves.

Contact updates, booking activity and notes have separate controls. Choosing a mapping does not turn those controls on. A mapped stage may create the contact it needs when none is linked; an existing linked contact can be used without updating its profile.

What Aura writes

Native calendar appointments, an optional origin tag, verified opportunity owner mapping and configurable meeting-link contact fields are separate improvements. Do not assume a stage update creates a native appointment or runs a reminder workflow.

Consent tags

Your booking form can ask people to agree to things, like reminder texts or offers by email. Aura tags each GoHighLevel contact with their answers, so your workflows can check them before texting or emailing. Aura always sends the phone number too, whatever the answers are.

To get these answers, give each of your consent boxes a type first. See Privacy & consent.

A contact gets one tag for each type. The tag ends with the answer:

• yes means they ticked the box. For texts, it counts only for the phone number they agreed with.
• no means they left the box unticked, or agreed and later took it back.
• not-asked means Aura has no answer of that type from them. Treat it like a no.

When an answer changes

Aura removes the old tag first, then adds the new one. So a contact never has two answers for one type. For example, when someone replies STOP to an Aura text, aura-booking-texts-yes comes off and aura-booking-texts-no goes on. This happens when their booking page shows Aura's own box for appointment texts.

If something goes wrong between the two steps, the contact may have no tag for that type for a while. Aura adds it when it tries again, or the next time that person's consent changes.

Things to know

• Aura writes consent to GoHighLevel only while at least one switch in Sync controls sends to GoHighLevel. With every one off, Aura adds and removes no consent tags and adds no notes.
• Aura adds tags only while Lead capture, Call booking or Won / lost outcome is on. With all three off but another switch on, Aura still removes a yes tag that is no longer true, but adds nothing.
• Aura only adds and removes these twelve tags. It never touches your other tags.
• If you make a tag with one of these names yourself, Aura treats it as its own answer.
• If you remove one of these tags by hand, Aura adds it back the next time that person's consent changes.
• While Lead capture, Call booking or Won / lost outcome is on, a contact with no answers on file gets all four not-asked tags. A workflow that starts when a tag is added runs once for each of them.
• While a switch sends to GoHighLevel, Aura also adds a note to the contact when the person has answered at least one box. It lists each box, the words the person saw and when they chose.

Aura passes the answers to GoHighLevel. It doesn't stop your team from texting or emailing from GoHighLevel. Check the tag before you send.

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 verified Aura-owned opportunity.
• Aura does not delete GoHighLevel records.
• Aura only adds or removes its own consent tags. Your other tags stay as they are.
• Disconnecting leaves all records already written to GoHighLevel in place.

Test environment

Use a dedicated GoHighLevel test agency and sub-account for controlled checks of OAuth, agency and location tokens, token refresh, contact and opportunity writes, webhooks, and disconnect and reconnect. Verify the resulting records in GoHighLevel before using the connection for customer workflows.

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 the lead's current Opportunities column, its saved mapping and Pipeline stages in Sync controls. A mapped pre-booking column can create a lead opportunity, and the first genuine booking can continue that opportunity. Aura stops when it cannot verify that an existing opportunity belongs to the connected account and lead.

I see Finish connecting GoHighLevel

Aura is installed in GoHighLevel but not linked to your Aura organization yet. Select Connect GoHighLevel and choose your sub-account.

GoHighLevel doesn't list my sub-account

GoHighLevel hides sub-accounts that already have Aura installed. To connect one:

1. In GoHighLevel, open the sub-account and remove Aura from its installed apps.
2. Wait until GoHighLevel lists the sub-account again. This can take about 30 minutes.
3. In Aura, select Connect GoHighLevel and choose the sub-account.

If the sub-account was connected to this Aura organization before, you can instead install Aura on it again from GoHighLevel after step 2. Aura links it back with your settings in place.

Aura says it was removed from your GoHighLevel account

Someone removed Aura from the sub-account in GoHighLevel. Your Aura settings are still saved. Once GoHighLevel lists the sub-account again, which can take about 30 minutes, install Aura on it again from GoHighLevel. Aura links it back to this organization.

The connection needs to be reconnected

GoHighLevel stopped accepting Aura's access. Your Aura settings stay saved. Because Aura is still installed, GoHighLevel won't list the sub-account under Connect GoHighLevel. Remove Aura from the sub-account in GoHighLevel. Once GoHighLevel lists it again, which can take about 30 minutes, install Aura on it again from GoHighLevel. Aura links it back to this organization.

Aura connected the wrong sub-account

Select Disconnect in Aura. Then remove Aura from the wrong sub-account in GoHighLevel. Select Connect GoHighLevel and choose the sub-account that belongs to this Aura organization.

What happens when I disconnect?

Aura stops all new sync activity and deletes this connection's settings, including your pipeline mapping. Existing contacts and opportunities stay in GoHighLevel.

Aura stays installed in GoHighLevel. Remove it from the sub-account in GoHighLevel too. Otherwise GoHighLevel won't list that sub-account if you want to connect it again.