# FAQ

<details>

<summary>Can I pull data from a white-labeled GoHighLevel URL?</summary>

Yes. Even if your agency uses a custom domain like `app.youragency.com`, Coupler.io authenticates through the standard GoHighLevel OAuth flow at `app.gohighlevel.com`. Enter your GHL credentials on that page and the connection will work normally.

</details>

<details>

<summary>Can I filter Opportunities by a specific pipeline?</summary>

Not directly — Coupler.io pulls all opportunities from your GHL account by default. To work with a specific pipeline, export all opportunities and filter them in your destination (e.g., using a Google Sheets filter or a Looker Studio filter control). You can also join Opportunities with Pipelines and then filter by pipeline name in your reporting tool.

</details>

<details>

<summary>Are GoHighLevel custom fields supported?</summary>

Yes. Custom fields are supported for **Contacts**, **Opportunities**, and **Companies**. Each custom field is returned as its own column — not a JSON blob. Custom fields on other objects (Tasks, Appointments, etc.) are not available through the GoHighLevel API.

</details>

<details>

<summary>How do I get pipeline names instead of pipeline IDs in my Opportunities data?</summary>

Add **Pipelines** as a second entity in your data flow and use a **Join** transformation on the `pipelineId` field. This replaces the raw ID with the human-readable pipeline name. See the data flow transformation docs for step-by-step instructions.

</details>

<details>

<summary>Can I pull data from multiple GoHighLevel sub-accounts into one destination?</summary>

Yes. Create a separate data flow for each sub-account, then use an **Append** transformation to combine them into a single sheet or table. Add a custom column in each flow to label which account the data belongs to.

</details>

<details>

<summary>Why are my timestamps off by one hour?</summary>

This is a timezone offset. GoHighLevel stores dates in a specific timezone, and if your destination or Looker Studio is configured for a different timezone, the times will appear shifted. Adjust the timezone in your destination settings or apply an offset formula to the date column.

</details>

<details>

<summary>Do I need to create a separate data flow for every GoHighLevel entity I want to export?</summary>

Not necessarily. A single data flow can contain multiple sources — you can add Contacts, Opportunities, and Pipelines as separate entities within the same data flow and apply Join or Append transformations to combine them.

</details>

<details>

<summary>Can I get call data, call durations, or outbound call timestamps from GoHighLevel?</summary>

Call-specific data (call status, duration, outbound timings) is not currently available as a standalone entity in the Coupler.io GoHighLevel integration. The **Conversations** entity returns messaging thread data but does not include detailed call logs. Check Coupler.io's changelog or contact support to ask about future entity support.

</details>

<details>

<summary>What happens if I accidentally delete custom formulas in my data flow?</summary>

Coupler.io does not currently have version history or formula recovery. If you clear changes or delete transformation formulas, they cannot be restored. Keep a backup of your formula logic outside of Coupler.io — for example, in a Google Doc or a notes file.

</details>

{% hint style="info" %}
For a full list of fields available per entity, see the [Data Overview](/sources/category/crm/gohighlevel/data-overview.md) page. For help with connection errors or missing data, visit [Common Issues](/sources/category/crm/gohighlevel/common-issues.md).
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.coupler.io/sources/category/crm/gohighlevel/faq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.