FAQ

Which Close.com plan do I need to use the API?

API access is available on Close.com paid plans. Free trials may have limited or no API access. Check your plan details in Close.com under Settings → API Keys — if you can generate a key, you have API access.

Where do I find my Close.com API key?

In Close.com, click your profile icon, go to Settings → API Keys, and generate a new key. Copy it immediately — Close.com won't show the full key again after you leave that page.

Can I connect multiple Close.com organizations to Coupler.io?

Yes. Each API key is scoped to one Close.com organization. If you manage multiple orgs, create a separate data flow for each one using the corresponding org's API key. You can then use the Append transformation to combine data from multiple orgs into a single destination.

How do I get rep names instead of user IDs in my reports?

Add the Users entity as an additional source in your data flow, then use the Join transformation to match the user_id (or assigned_to) field on your activity or lead entity with the id field on Users. This will resolve IDs to names and email addresses.

Can I pull data from a specific date range only?

Yes. When configuring your source in Coupler.io, use the date picker in the Start date field to set the earliest date for data retrieval. Leave it blank to pull all available historical data.

Why does the Events entity take so long to sync?

The Events entity logs every action across your Close.com account and can be extremely large for active teams. Set a start date to limit the volume, and consider routing this entity to BigQuery rather than Google Sheets for better performance.

Can I use Close.com data with AI tools?

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your leads, opportunities, or call activity data directly to these tools for analysis, summarization, or forecasting.

What's the best way to build a pipeline report?

Start with the Opportunities entity and join it with Pipelines (on pipeline_id) and Users (on user_id). Use Coupler.io's Aggregate transformation to group by pipeline stage and sum the value field (remember to divide by 100). Send the result to Looker Studio or Google Sheets for visualization.

Why are my custom field columns showing IDs instead of field names?

Close.com uses internal IDs for custom field column headers. Pull the matching custom fields definition entity (e.g., Lead custom fields) and join it to your main entity on the field ID to get human-readable names. See the Data Overview for more detail.

For a full list of available fields per entity, see the Data Overview. For help with sync errors or missing records, visit Common Issues.