--- title: "CallRail Integration" description: "Connect AI agents to CallRail call tracking and marketing attribution. Agents pull tracked calls, form submissions, and text conversations, tie each lead to the campaign and keyword that drove it, update tags, values, and lead status, and manage companies and tracking numbers." url: https://flowrunner.ai/integrations/callrail date_modified: 2026-08-07T17:20:23-07:00 --- # CallRail [Analytics & Data](https://flowrunner.ai/integrations/category/analytics-data) Connect AI agents to CallRail call tracking and marketing attribution. Agents pull tracked calls, form submissions, and text conversations, tie each lead to the campaign and keyword that drove it, update tags, values, and lead status, and manage companies and tracking numbers. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 31 actions · API key · available [CallRail website](https://callrail.com/) · [Platform Documentation](https://apidocs.callrail.com/) · Capability data verified 2026-07-27 1. Morning schedule opens the daily lead review run 2. List Calls pulls yesterday's first-time callers with attribution 3. Get Call retrieves recordings and Conversation Intelligence fields 4. Each caller matched against existing leads to skip repeat contacts 5. Update Call sets lead status, tags, and estimated value 6. Slack summary lists qualified callers by campaign and keyword 7. Rep approves the follow-up text before Send Text Message fires ## What This Integration Enables CallRail answers a question most analytics stacks cannot: which campaign made the phone ring. This integration is built on the view that attribution data is only worth what you do with it the same day. Agents pull tracked calls, form submissions, and text conversations with the source, campaign, keyword, and landing page attached to each one, then do the enrichment work that never survives a busy week: setting lead status, applying tags, assigning monetary value, and flagging spam so it drops out of reporting. Get Call Summary lets an agent group call metrics by any attribution dimension, which turns "how did the campaign do" into a scheduled workflow instead of a request to the marketing team. The connector also acts. Agents provision companies, tracking numbers, and tags as new clients or campaigns come online, place tracked outbound calls, and send SMS replies from texting-enabled tracking numbers. The outbound surface is exactly where [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) earns its place: a text that reaches a customer, or a tracker deletion that releases a phone number, goes through a person first. Connector capabilities are built and verified against CallRail's official API. ### Without FlowRunner **Calls without a verdict**: Tracked calls pile up with no lead status, tags, or value assigned **Attribution as a monthly report**: Campaign and keyword data gets reviewed long after budget decisions are due **Missed calls, missed leads**: Unanswered first-time callers get no follow-up unless someone notices ### With FlowRunner **Every call scored**: Lead status, tags, and value land on each call the day it happens **Attribution in the daily loop**: The campaign behind each qualified caller is visible while it still matters **Follow-up with a gate**: A drafted text goes to the rep for approval, then out from the tracked line ## Use Case Scenarios ### Daily lead triage from the call log Each morning an agent runs List Calls for the previous day, filtered to first-time callers, and pulls Get Call for recordings and Conversation Intelligence fields. It matches callers against existing leads, then uses Update Call to set lead status, apply tags, and assign an estimated value based on what the call covered. The qualified list posts to [Slack](https://flowrunner.ai/integrations/slack) grouped by campaign and keyword, and for callers who did not connect, the agent drafts a follow-up text. The rep approves each draft before Send Text Message delivers it from the same tracked number the customer originally dialed. ### Agency client provisioning without the setup backlog An agency signs a new client in the CRM. The agent calls Create Company to set up the client's reporting container, Create Tracker to provision tracking numbers for each campaign channel, and Create Tag to lay down the taxonomy the account team will filter by. When the engagement details change, Update Company and Update Tracker keep routing and attribution current. The account manager gets a summary in [HubSpot](https://flowrunner.ai/integrations/hubspot) with the new tracker numbers, and client onboarding stops competing with client work. ### Attribution reporting that lands where budgets get set On a weekly schedule, an agent calls Get Call Summary grouped by source, campaign, and keyword, plus List Form Submissions for the same period so calls and forms report as one lead stream. It appends the results to a running report with [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and posts the movers to the marketing channel: which campaigns drove qualified calls, which drove volume without value. When a number consistently produces spam, the agent flags the calls through Update Call and queues the tracker for review rather than deleting anything on its own. ## Human-in-Loop Highlight Delete Tracker permanently releases a tracking number. CallRail cannot bring it back: call tracking on that number stops, and any ad, listing, or website still displaying it now rings nowhere. So the cleanup agent never deletes a tracker on its own. When it finds trackers with no calls in the review window, it posts the candidates to the operations channel: "3 trackers had zero calls this quarter: \[numbers, companies, sources\]. These numbers may still be printed on live ads or directory listings. Confirm which to release." A person who knows where those numbers appear makes the call. The agent handles the audit; the human owns the irreversible release. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 31 actions ### Accounts 2 - **List Accounts** Lists all CallRail accounts accessible to the API key. Used to discover the account ID that scopes every other operation. - **Get Account** Retrieves a single account with its settings, including outbound recording and HIPAA status. Used to confirm compliance posture before recording-related workflows. ### Calls 4 - **List Calls** Lists tracked calls with filtering by date range, company, tracker, call type, answer status, direction, device, lead status, and tags. The workhorse for daily triage and reporting runs. - **Get Call** Retrieves full detail for a single call including caller information, recording, attribution, and Conversation Intelligence fields such as transcripts. Used when a workflow needs what was actually said. - **Create Outbound Call** Initiates a tracked click-to-call: CallRail rings the agent first, then dials the customer. Used to launch callbacks that stay inside attribution reporting. - **Update Call** Updates a call's notes, tags, value, lead status, customer name, and spam flag. Used to score and enrich every call the day it happens; marking spam removes it from billing and reports. ### Reporting 1 - **Get Call Summary** Retrieves aggregated call metrics grouped by source, campaign, keywords, referrer, landing page, or company. Used for scheduled attribution reports. ### Companies 5 - **List Companies** Lists the companies configured in an account. Used to resolve the right client or business unit before scoped operations. - **Get Company** Retrieves a single company with its status, time zone, and configuration. - **Create Company** Creates a company to group tracking numbers and reporting for a business or client. Used in agency client onboarding. - **Update Company** Updates a company's name, time zone, status, or cookie-swap configuration. - **Delete Company** Permanently deletes a company and its tracking configuration. Cannot be undone; workflows route this through human approval. ### Trackers 5 - **List Trackers** Lists tracking numbers with their routing and source configuration. Used for audits and cleanup reviews. - **Get Tracker** Retrieves a single tracker with its type, destination number, and status. - **Create Tracker** Creates a tracking number that forwards to a destination while capturing source attribution. Used to provision campaign channels. - **Update Tracker** Updates a tracker's name, destination, owning company, type, or swap target. - **Delete Tracker** Permanently releases a tracking number and stops tracking on it. The gated action in this connector: a human confirms before any number is released. ### Form Submissions 3 - **List Form Submissions** Lists web form submissions captured alongside calls for unified lead attribution. Used to report calls and forms as one lead stream. - **Get Form Submission** Retrieves a single submission with field data, attribution source, and lead status. - **Update Form Submission** Updates a submission's lead status, tags, note, and value. Used to score form leads with the same discipline as calls. ### Text Messages 3 - **List Text Conversations** Lists SMS and MMS conversations grouped by customer and tracking number. Used to find threads awaiting a reply. - **Get Text Conversation** Retrieves the full message thread with a customer. - **Send Text Message** Sends a text from a texting-enabled tracking number to a customer. Outbound to a real person, so drafts go through rep approval before sending. ### Users 2 - **List Users** Lists account users with names, emails, and roles. Used to route notifications to the right owner. - **Get User** Retrieves a single user with role and permission details. ### Tags 4 - **List Tags** Lists the tags defined in an account. Used to keep workflow tagging consistent with the existing taxonomy. - **Create Tag** Creates a tag with a display color, optionally scoped to a company. - **Update Tag** Updates a tag's name or color. - **Delete Tag** Permanently deletes a tag and detaches it from every call and form it was applied to. Cannot be undone; used only in reviewed cleanup. ### Integrations 2 - **List Integrations** Lists the third-party integrations configured on the account, such as Google Analytics or Salesforce. Used to understand where CallRail data already flows before adding a workflow. - **Get Integration** Retrieves a single integration's type, state, and configuration. ## Frequently Asked Questions ### What can FlowRunner do with CallRail? FlowRunner agents can run List Accounts, Get Account, and List Calls in CallRail, plus 28 more actions. ### Does connecting CallRail to FlowRunner require OAuth? No. CallRail connects to FlowRunner with an API key, no OAuth flow required. ### Can CallRail trigger a FlowRunner workflow automatically? CallRail doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at CallRail?** This integration exposes CallRail to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/callrail. Site index: https://flowrunner.ai/llms.txt