FAQ

Where do I find my CallRail API key?

Log in to CallRail and go to Settings > API Access. Your API key is listed there. If you don't see this option, your plan may not include API access — contact CallRail support to confirm.

Can I connect multiple CallRail accounts to one data flow?

Yes. Add each account as a separate source within the same data flow using its own API key, then use the Append transformation to combine the data into one table. This is especially useful for agencies managing multiple client accounts.

What's the difference between Calls and Conversations?

The Calls entity contains individual inbound and outbound call records. The Conversations entity is broader — it groups interactions across channels (calls, SMS, live chat) into threaded conversation records. Use Calls for pure call analytics and Conversations if you want a unified view of all customer touchpoints.

Can I pull data for a specific tracking number only?

CallRail's API doesn't support filtering by tracking number at the source level. Pull all calls and filter by tracking number in your destination (e.g., using a filter in Google Sheets or a WHERE clause in BigQuery).

Why are some calls showing no source or campaign data?

Source, medium, and campaign fields are only populated when CallRail's JavaScript snippet is active on your website and the caller arrived via a tracked session. Direct calls to a static number — or calls where the session wasn't tracked — won't have attribution data.

Can I use CallRail data with AI tools?

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your call or conversation data directly to these tools for summarization, lead scoring, trend analysis, or automated reporting commentary.

How far back can I pull historical call data?

There's no hard limit set by Coupler.io — use the date picker in the Start date field to set how far back you want to go. Very large date ranges covering years of high-volume call data may take longer to process on the first run.

For details on what fields are available in each entity, see Data Overview. If your data flow isn't returning expected results, check Common Issues for troubleshooting steps.