HighLevel CRM beta
HighLevel is available in beta as a CRM Connected Account in OutboundSync. This beta is one-way only: activity flows from your sales engagement platform into HighLevel. Each mapped event finds or creates a Contact and writes a plain-text Note on that Contact.
Connect HighLevel from CRM Settings in OutboundSync with Location (sub-account) OAuth. Source setup and the first test Note are handled with the OutboundSync team.

What this beta does today
Section titled “What this beta does today”- Connect a HighLevel Location as a CRM connection in OutboundSync.
- Find or create a HighLevel Contact, then write each mapped event as a plain-text Note on that Contact.
- Sync one-way outbound email activity as Notes.
- Sync one-way outbound social activity as Notes.
- On match, refresh name, phone,
companyName, and configured custom fields. Email is never updated (it is the dedup key). - On duplicate Contacts, the oldest
dateAdded/createdAtwins. - Write the note author from the configured owner. The Contact assignee is never set.
- Guide source setup and the first test Note with the OutboundSync team during beta.
Current beta limits
Section titled “Current beta limits”- One-way sync only.
- Writes Contact and Note only. Companies, opportunities, pipelines, tasks, tags, and custom objects are not part of the beta. Company is the Contact string
companyName. - Email + social supported; phone is not supported in this beta.
- Custom fields are for lookup and social-profile URL write-back only — not HubSpot-style property sync.
- Block lists are not part of the HighLevel beta.
- Less configurability and less depth than HubSpot and Salesforce today.
- Source setup and exact event coverage are confirmed with the OutboundSync team.
Lookup methods
Section titled “Lookup methods”How OutboundSync matches the Contact depends on the source:
- Email SEPs. Lookup is locked to email.
- Social and hybrid SEPs. Lookup uses
default,alternative_property, oroptional_alternative_propertyagainst HighLevel custom fields. Point those fields at the property that stores the social profile URL. - Custom field. Optional-alternative lookup tries that field first, then falls back to email or the social profile URL.
Notes and default properties are required and locked on.
The HighLevel email used for Location OAuth must match the OutboundSync user. The app rejects a mismatch.
Note body
Section titled “Note body”Each Note is plain text (lines.join('\n')), not HTML. Sends and replies are Notes — not native email activities or Conversations. Typical lines:
OutboundSync {event_type}- Platform
- Lead email
- Social profile
- Company
- Campaign
- App URL
- Message text (
reply_message/sent_message/message_text/connection_message/post_url)
From, To, CC, and subject are not written.
Supported platforms
Section titled “Supported platforms”HighLevel beta currently supports these platforms direct:
- Smartlead
- Instantly
- Clay
- EmailBison
- Brevo
- Reply.io
- Lemlist
- Aimfox
- Drippi
- HeyReach
- Mixmax
- SalesRobot
- Salesforge
- GetSales
- Ken AI
- SuperSend
- HotHawk
- Master Inbox
Expandi, Salesflow, PlusVibe, and Ashby flow into HighLevel through Master Inbox.
HighLevel filters and views
Section titled “HighLevel filters and views”Teams can use synced Notes on Contacts inside the filters and views they build in HighLevel. OutboundSync does not ship prebuilt filters or views as part of the current beta.
Event coverage during beta
Section titled “Event coverage during beta”Exact event coverage is confirmed during onboarding and the first test Note. Use the setup guides below where they already exist, then validate the final flow on a real HighLevel Contact with the OutboundSync team.
How onboarding works
Section titled “How onboarding works”- Book a demo with the OutboundSync team.
- Connect HighLevel as a Connected Account in OutboundSync. Authorize the HighLevel Location (sub-account). The OAuth email must match the OutboundSync user.

- Work with the OutboundSync team to create the HighLevel source and select your platform.
Email sources lock lookup to email. Notes and default properties stay required. Social and hybrid sources match on a HighLevel custom field for the social profile URL.
- Run a test sync and review the Note on a real HighLevel Contact.

Existing setup guides
Section titled “Existing setup guides”Use the current webhook/setup guides below where they already exist: