> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/crm/gohighlevel/best-practices.md). # Best Practices ## Recommended setup


Join Opportunities with Pipelines	The Opportunities entity returns pipeline IDs, not names. Add Pipelines as a second source in the same data flow and use a Join transformation on `pipelineId` to make your reports human-readable.
Use Append for multi-account reporting	If you manage multiple GoHighLevel sub-accounts, create one data flow per account and use Append to stack them into a single destination sheet or table. Add a custom column to tag each row with the account name.
Join Contacts with Opportunities	Opportunities don't include contact details like email or lead source. Join on `contactId` to enrich your deal data with contact-level attributes for deeper sales analysis.

## Data refresh and scheduling


Always run manually first	A successful manual run is required before you can set up a schedule. Use the first run to verify row counts and check that custom fields are appearing as expected before automating.
Match refresh frequency to your reporting needs	Sales dashboards updated throughout the day benefit from 15-minute or hourly refreshes (Business plan). Weekly revenue or invoice reports don't need frequent syncs — daily is usually enough and keeps API usage lower.

## Performance optimization


Filter Appointments and Tasks by Contact ID	If you only need data for specific contacts, enter their Contact IDs in the parameter field. This fetches far fewer records than pulling all appointments or tasks across the account.
Don't run overlapping flows for the same account	Running multiple data flows against the same GoHighLevel account at the same time increases the risk of hitting GHL's API rate limits. Stagger your schedules by at least a few minutes.

## Common pitfalls {% hint style="danger" %} Custom fields are only available for Contacts, Opportunities, and Companies. If you build formulas or transformations expecting custom fields from other objects (like Tasks), those fields won't appear — the GoHighLevel API doesn't expose them. {% endhint %} {% columns %} {% column %} **Do** * Join Opportunities + Pipelines to get readable pipeline names * Use Contact IDs to scope Appointments and Tasks to specific records * Verify row counts on the first manual run before scheduling * Store formula logic somewhere outside Coupler.io — there is no version history or formula recovery if changes are lost {% endcolumn %} {% column %} **Don't** * Expect custom fields from objects other than Contacts, Opportunities, or Companies * Run multiple flows against the same GHL account at the same time * Assume a timestamp offset is a data bug — check timezone settings first * Connect at sub-account level if you need cross-account reporting {% endcolumn %} {% endcolumns %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.coupler.io/sources/category/crm/gohighlevel/best-practices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.