Common Issues

Connection issues

My API key is rejected when connecting

Double-check that you copied the full API key from Close.com without any leading or trailing spaces. In Close.com, go to Settings → API Keys and generate a new key if needed. Also confirm that your Close.com plan includes API access — the API is available on paid plans only.

The data flow fails immediately after connecting

This often happens if the API key belongs to a user with limited permissions. Try using an API key generated by an admin user. Also check whether your Close.com organization has API rate limits that might be cutting off the initial request.

Missing data

Some leads or opportunities are missing from my sync

If you set a start date, only records created or updated after that date will sync. Use the date picker to adjust the range, or clear the start date entirely to pull all available data. Also check whether the missing records belong to a different Close.com organization — each API key is scoped to one org.

Custom field values are blank on lead or contact records

Custom field values are included in the Leads, Contacts, or Opportunities entity output, but the column names use the internal field ID rather than the display name. Pull the corresponding custom fields entity (e.g., Lead custom fields) to get a mapping between field IDs and their labels, then use a Join transformation to resolve the names.

The Events entity returns no data

The Events entity can return a very large dataset. If you didn't set a start date, the sync may be timing out before it completes. Use the date picker to set a recent start date and reduce the volume of records being pulled.

Permission errors

I'm getting a 403 or "unauthorized" error on certain entities

Some entities — particularly bulk action logs and admin-level configuration entities — may require admin-level API access. If your API key belongs to a standard user, try regenerating the key as an admin user in Close.com under Settings → API Keys.

Data discrepancies

Opportunity values in Coupler.io don't match what I see in Close.com

Close.com stores opportunity values in cents (e.g., $1,500 = 150000). Divide the value field by 100 in your destination to get the correct currency amount. You can do this directly in a Google Sheets formula or as a calculated field in Looker Studio.

User names are showing as IDs instead of names

Most activity and lead entities store the rep reference as a user_id. Add the Users entity as a second source in your data flow and use the Join transformation to match user_id to the user's name and email.

Rate limits

My sync is slow or stops partway through large entities

Close.com's API enforces rate limits, especially for large orgs with many leads or events. If you're syncing a high-volume entity like Events or Call activities, set a start date to limit the data range per run. For very large historical pulls, consider syncing in chunks by adjusting the start date across multiple data flows.