Connect GoHighLevel to Nod

Before you start

You need Operations Pro, administrator access, and permission to connect the GoHighLevel subaccount. Agent features also require a Nod AI plan.

Step by step

1. Open Integrations → GoHighLevel → Configure. Select Connect with GoHighLevel and authorize the subaccount you want to link to this business.
2. Back in Nod, open the GoHighLevel settings. Review What syncs: contacts and stages have separate controls for each direction; appointments and payments are received from GoHighLevel.
3. Under Match stages, choose the Nod stage for each GoHighLevel stage and select Save matching. Unmapped stages do not sync.
4. Review where Nod leads are created. If a Nod Pipeline maps to multiple destinations, choose the destination and save it.
5. Check the log and review an existing contact without creating duplicates. Nod contacts need an email address or phone number to be sent to GoHighLevel.

Contacts: what syncs and what does not

Name, email, phone, company, and tags follow the enabled sync directions. Custom fields do not sync. If the same detail changes in both systems, the most recent change wins.

A Nod contact without an email or phone number is not sent to GoHighLevel. It is sent once either is available. Turning off new contact exports does not by itself stop stage updates for contacts already linked.

Stages, destinations, and closed opportunities

Under “Match stages,” choose a Nod stage or “Don’t sync” and save each pipeline with “Save matching.” Enable the required directions under “What syncs.”

Under “Where Nod leads are created,” choose a destination when a Nod Pipeline maps to several GoHighLevel pipelines, then save destinations. A missing destination or unmapped stage prevents the corresponding opportunity from being created.

Won and lost are opportunity statuses in GoHighLevel. Moving a lead to those Nod columns updates an existing opportunity in the destination; it does not create a new closed opportunity. Returning to a mapped stage can reopen it.

Opportunity value and contact notes

The lead’s expected deal value syncs with the opportunity value. The most recent change wins. Clearing a value previously sent by Nod sets it to zero in GoHighLevel; a value set only there is not cleared simply because Nod has no amount.

Contact notes travel from Nod to GoHighLevel when that contact direction is enabled. Editing updates the same note; clearing the text removes it there. Notes written in GoHighLevel do not return to Nod. This note is separate from the Instagram conversation note.

Appointments and payments: direction and limits

GoHighLevel appointments appear in Calendar, Sales → Calls, and the lead record. The closer is matched using the same user email in both systems. The initial import includes appointments from 30 days ago through 90 days ahead.

Appointments created from a Nod contact record or Calendar are not created in GoHighLevel. Nod AI automatic scheduling also cannot complete bookings there until appointment creation permission is enabled.

Paid invoices and orders become sales. Pending orders are not sales. Order refunds are received, but invoice refunds are not because GoHighLevel does not notify Nod of them. Payments travel only from GoHighLevel to Nod.

Nod AI tags and conversation notes

With Operations Pro and any Nod AI plan, enable “Agent tags” and “Instagram conversation as a note,” review the tag names, and save. The note contains up to the last 40 messages, capped at 5,000 characters.

Qualification, booking-link-sent, and review tags can trigger GoHighLevel workflows. A sent booking link does not prove that an appointment was booked.

Adding the configured AI handoff, team handoff, or exclusion tag in GoHighLevel controls the Instagram conversation. AI handoff requires an active agent and an approved playbook. Exclusion removes the conversation from the Inbox while the tag remains.

Troubleshooting, reimporting, and disconnecting

Check the status and log to distinguish applied, queued, and unapplied changes. “Last sent to GoHighLevel” describes the Nod → GoHighLevel direction.

“Import again” repeats the initial import and matches existing records. “Disconnect” stops syncing but keeps contacts in both systems. Downgrading from Pro keeps the connection but stops syncing.

“Remove contacts sent by Nod” deletes records in GoHighLevel; it is not just a disconnect action. It removes the contacts created by Nod and their opportunities, preserves pre-existing contacts, and turns off new contact exports. It does not delete Nod contacts. Read the confirmation and review progress under Settings → Automatic jobs.

What to expect

HighLevel contacts display its logo in Nod. Stages and data follow the enabled sync settings. Opportunities reflect won or lost outcomes.

Troubleshooting

Check the subaccount, sync direction, and mapping before reconnecting. Do not manually record a payment just because it is not visible yet. Disconnecting stops sync and removes tokens, but does not automatically delete synchronized records. Removing contacts created by Nod is a separate action.