Kokeile ilmaiseksi
Kokeile ilmaiseksi
Alustan dokumentaatio

HighLevel CRM - Setup & usage

Viimeksi päivitetty {päivämäärä}

HighLevel CRM - Setup & usage

Connect OAuth

  • Open Workspace Settings → Integrations and connect the correct brand (Momentum Engine, LeadConnector, or HighLevel CRM).

  • Complete the provider consent screen and select the location (sub-account) to link.

  • Elevale stores the location ID on the connection and uses it for every API call.

  • If location ID was missing on an older connection, the first sync resolves it from the HighLevel locations API and saves it.

  • The connection appears under Connected integrations when active.

Create connected KPIs

  • On KPIs & Dashboards, create or edit a KPI and choose Connected as the type.

  • Select your Momentum Engine, LeadConnector, or HighLevel CRM connection.

  • Pick a data point from the list - opportunity metrics, lost-by-reason entries, contacts, conversations, appointments, or payments.

  • Choose a sync frequency (daily, weekly, monthly, etc.).

  • Save the KPI; an initial sync runs automatically. Use Resync on the KPI card to pull fresh data on demand.

Troubleshooting

  • Blank OAuth page - confirm you connected the brand that matches your HighLevel install domain (Momentum Engine/LeadConnector vs HighLevel CRM).

  • Invalid scope error - platform OAuth scopes must use current HighLevel scope names (for example payments/transactions.readonly, not deprecated payments.readonly). Contact your administrator if Connect fails at consent.

  • Failed to fetch data / 422 on contacts - usually caused by unsupported query parameters on GET /contacts/. Count-based contact KPIs should work; date-filtered contact KPIs may fail until search API support is added.

  • 504 / Request idle timeout - opportunity value KPIs on very large pipelines. Retry after off-peak hours or split into smaller filtered KPIs (for example won value only).

  • Location ID not found - disconnect and reconnect, ensuring you select a location during OAuth.

  • Lost reason data points missing - your location may have no configured lost reasons in HighLevel, or the lost-reasons API returned empty. Add lost reasons in HighLevel CRM settings.

  • Sync succeeded but value looks wrong - check whether the metric is a count (meta.total) or a paginated sum (capped at 2,000 rows). Verify status filters match how deals are staged in HighLevel (open vs won vs lost).

Disconnect and privacy

  • Disconnect from Workspace Settings → Integrations to revoke stored OAuth tokens and stop scheduled syncs.

  • Previously synced KPI history remains until you delete or convert those KPIs.

  • Integration data is used only to populate KPIs and dashboards in your workspace.

  • Subprocessors and data handling are described in Subprocessors and integrations.

Disconnect and data retention