> 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/sales/callrail.md).

# CallRail

CallRail is a call tracking and analytics platform that helps businesses understand which marketing campaigns are driving phone calls and conversions. It gives you visibility into call volume, caller details, conversation quality, and team performance — all in one place.

Connecting CallRail to Coupler.io lets you pull your call and conversation data into spreadsheets, dashboards, or data warehouses without any manual exports. You can combine it with CRM or ad data to build a full picture of your marketing ROI.

**Why connect CallRail to Coupler.io?**

* Export calls, conversations, users, and companies to Google Sheets, Excel, BigQuery, or Looker Studio automatically
* Send call data to AI tools like ChatGPT, Claude, or Gemini for summaries, scoring, or trend analysis
* Join call data with ad spend or CRM records to measure true cost-per-lead
* Append data from multiple CallRail accounts into a single unified report

## Prerequisites

Before connecting, make sure you have:

* An active CallRail account (any paid plan)
* A CallRail API key — found in your account under **Settings > API Access**
* Read-level access to the data you want to export

## Quick start

{% hint style="success" %}
Start with the **Calls** entity to get your core call log data, then add Conversations in the same data flow if you need full transcript and messaging data alongside it.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to your Coupler.io account and click **Add data flow**. Search for **CallRail** and select it as your source.
{% endstep %}

{% step %}
**Enter your API key.** In CallRail, go to **Settings > API Access** and copy your API key. Paste it into the API key field in Coupler.io.
{% endstep %}

{% step %}
**Select an entity.** Choose what data you want to pull — Calls, Conversations, Users, or Companies. You can add more sources to the same data flow later.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to choose the earliest date you want data from. This controls how far back Coupler.io will pull records.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want the data to go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute your first manual sync. Once it completes successfully, you can set up a schedule to keep data refreshing automatically.
{% endstep %}
{% endstepper %}

## Available entities

| Entity        | What it contains                                                        |
| ------------- | ----------------------------------------------------------------------- |
| Calls         | Individual call records with caller info, duration, source, and outcome |
| Conversations | Multi-channel conversation threads including calls, texts, and chats    |
| Users         | Team members and agents in your CallRail account                        |
| Companies     | Company records associated with your CallRail account                   |


---

# 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/sales/callrail.md?ask=<question>&goal=<endgoal>
```

`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.