Common Issues

Connection issues

OAuth redirects to the wrong GoHighLevel URL

If you use a white-labeled GoHighLevel domain (e.g., app.youragency.com), Coupler.io will still redirect to the standard app.gohighlevel.com for authentication. This is expected — GoHighLevel's OAuth flow requires the official domain. Log in with your GHL credentials on that page and authorization will complete normally.

I can't see my agency sub-accounts after connecting

GoHighLevel authentication scope depends on your account type. If you connected as a sub-account user, you'll only see that sub-account's data. To access multiple sub-accounts, connect using your agency-level credentials. If you need data from several sub-accounts in one destination, create separate data flows and use an Append transformation to combine them.

The data flow connects but returns no data

This can happen if the connected account has no records for the selected entity, or if the OAuth token has expired. Try disconnecting and reconnecting your GoHighLevel account, then run the data flow again. If the issue persists, check that your GHL account has data for the entity you selected.

Missing data

Custom fields aren't showing up as columns

Custom fields are only available for Contacts, Opportunities, and Companies. If your custom fields were created under a different object in GoHighLevel (e.g., Tasks or Appointments), they won't appear — the GHL API does not expose them for those objects. Also confirm that the fields are populated in GHL, as empty custom fields may not be returned.

Opportunities aren't exporting any rows

This is a known issue that has been addressed in a fix. If you're still seeing no rows for Opportunities, try reconnecting your GoHighLevel account and running the data flow again. If the problem persists, contact Coupler.io support with your data flow name.

Appointments or Tasks are missing records I expect to see

Appointments and Tasks use filter parameters. If you set a start date, only records for contacts created after that date are returned. If you entered Contact IDs, only those contacts' records are returned and the start date is ignored. Check your parameter settings to confirm the filter matches what you expect.

Only a small percentage of my data is showing

This is usually a temporary API delay or a pagination issue during a sync. Run the data flow again manually — if the row count stabilizes, it was a transient hiccup. If the problem repeats consistently, contact support with your data flow name and a screenshot of the row count.

Data discrepancies

Timestamps are off by one hour compared to GoHighLevel

GoHighLevel stores dates in a specific timezone. If your destination or Looker Studio is set to a different timezone, dates can appear shifted by one hour. This is a timezone offset, not a data error. Adjust the timezone in your destination settings or apply a date formula to offset the values.

AssignedTo field shows an ID instead of a name

The assignedTo field returns a GoHighLevel user ID, not a display name. This is how the GHL API returns the value. To display names, you'll need to cross-reference IDs manually or build a lookup using a separate user list. Coupler.io does not currently offer a dedicated Users entity.

Data in Looker Studio doesn't match what I see in GHL

Looker Studio can display a "bad reaggregation" warning that is a Looker Studio UI bug — no actual data re-aggregation is occurring. For genuine discrepancies, go to your data flow in Coupler.io and check the most recent run's row count against your GHL record count. If there's a real mismatch, contact support.

Rate limits

My data flow is slow or times out on large accounts

GoHighLevel's API has rate limits that affect how quickly large datasets can be fetched. If you have a very large number of contacts or opportunities, the sync will take longer. Avoid running multiple data flows for the same GHL account simultaneously, as this increases the chance of hitting rate limits.