CallTrackingMetrics
Voice & TelephonyConnect AI agents to CallTrackingMetrics, a call tracking and contact center platform. Agents read call records and recordings, attribute calls to tracking numbers and sources, record call sales, sync contacts, and read agent activity.
What This Integration Enables
CallTrackingMetrics answers one question that most analytics stacks cannot: which marketing spend produced the phone call. It does that by handing out tracking numbers, matching inbound activity to sources, and holding the whole contact center layer of agents, tags, contact lists and FormReactors alongside it. This connector is deliberately weighted toward reading that data and moving it somewhere the rest of the business already works.
The write surface is small and worth naming precisely, because it is where the value and the risk both sit. Agents can update the contact fields on an activity record with Update Call, create and update contacts in the account address book, and record a sale against a call with Record Call Sale. Everything else reads: the activity feed, tracking numbers and sources, agents and their event timelines, users, tags, contact lists, saved reports and FormReactors. That is a good shape for a system of measurement. A connector that could reconfigure your number routing from an automated condition would be a worse thing to own than one that cannot.
Two boundaries to design around. This connector has no triggers. CallTrackingMetrics does expose a webhook subscription API, but the delivered event payload is not publicly documented, so a trigger could not be built against a shape nobody publishes. Webhooks appear here as the read-only List Webhooks action, which inventories the outbound webhooks your account already sends to wherever they already point. Listing them creates nothing in FlowRunner and subscribes to nothing. A flow that reacts to call activity is polling List Calls over a date range, and your polling interval is your latency. Second, reporting: List Reports returns the saved report definitions configured in the account, meaning their IDs, names and configuration, so a flow can reference or review them. No action executes a saved report or returns its aggregated numbers. Agent-level reporting is real and granular through List Agents and Get Agent Events; channel-level reporting is something you assemble from the raw activity rather than something you fetch.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The activity feed becomes a table other people can use
A nightly flow calls List Calls for the previous day with a date range, which returns not just phone calls but texts, chats and form submissions in one feed, each record carrying caller details, source, duration, tags and the recording URL where one exists. The agent normalizes each record and appends it to Google Sheets or pushes it into the warehouse. The reason this is worth automating is not that the export is hard. It is that a monthly manual export gets skipped in busy months, and the gap always shows up later as a quarter that cannot be analysed. Set the Account parameter explicitly on every call, since agency keys can reach every sub-account under the agency while account-level keys are confined to their own.
Contact records that stop drifting
Call tracking builds an address book as a side effect of people calling you, and it goes stale the moment your CRM knows something newer. A flow reads contact updates from HubSpot, calls List Contacts with a free-text search on the phone number to find the matching record, and calls Update Contact with the current name, email and notes, or Create Contact when no match exists so the next inbound call attaches to a known person rather than a bare number. For activity records that already happened, Update Call writes the corrected caller name, email and mailing address onto the call itself, which is what makes a six month old recording findable by the name of the person on it.
A staffing picture built from what agents actually did
List Agents returns the contact center agents with their availability status and settings, and Get Agent Events returns a single agent's timeline of status changes, logins and logouts and call handling inside a window, keyed by the internal user ID you get from List Users. A weekly flow walks the agent list, pulls each timeline for the week in epoch seconds, and assembles a picture of coverage against inbound volume from List Calls: when the queue was busiest, who was available, where the gaps landed. It posts the summary to the operations channel in Slack. This is reporting the console can show one agent at a time and that nobody assembles across the team because it takes an afternoon.
Human-in-Loop Highlight
Record Call Sale is the one write in this connector that changes what the business believes. It attaches a conversion flag, a sale value, an optional lead score and a label to a call, and that record feeds CallTrackingMetrics conversion and ROI reporting, which is to say it feeds the report someone uses to decide where next quarter's budget goes. There is no action in this connector that removes or reverses a recorded sale. Attribution written in error does not announce itself either: a deal attached to the wrong call quietly credits the wrong tracking source, the wrong campaign gets a better cost per acquisition than it earned, and the correction has to happen inside CallTrackingMetrics by hand once someone notices the channel mix looks odd. Matching deals to calls is also genuinely ambiguous work, because a customer who called three times from two numbers across five weeks has three candidate calls and only one of them is the one that mattered. So the agent does the matching and stops before the write. It pulls the candidate calls with List Calls filtered on the customer's number, enriches each with Get Call so the message carries the tracking number, the source and the date, and asks: "Closed deal for Riverside Dental, 4,800 dollars. Three candidate calls: 12 July from Google Ads paid search, 19 July from organic, 2 August from direct mail. Which call gets the sale, and at what value?" A person picks, and the agent calls Record Call Sale against exactly that call ID. The tedious part, finding and assembling the candidates, was never a judgment call. The attribution always was.
Agent Capabilities
21 actionsAccounts
1- List Accounts Lists every CallTrackingMetrics account your credentials can reach. Agency keys return every sub-account under the agency; account-level keys return only their own. The numeric account ID returned here is the Account parameter every other operation takes.
Calls and Activity
4- List Calls Lists activity records for an account, newest first, covering phone calls, texts, chats and form submissions in a single feed. Supports date-range filtering, a free-text filter matching caller name, number, tags and notes, and pagination. Each record includes caller details, source, duration, tags and the recording URL when one is available. With no triggers available, this is the polling surface for inbound activity.
- Get Call Retrieves the full detail of a single activity record by ID: caller information, tracking and business numbers, source attribution, tags, notes, sale and conversion data, and the recording URL. Use the ID returned by List Calls.
- Update Call Updates the editable contact fields stored on an activity record, such as the caller's name, email, mailing address and notes. Only provided fields change. This is how a call recorded against a bare phone number becomes findable by the name of the person on it.
- Record Call Sale Records a sale or conversion against a call, attaching a conversion flag, a sale value, an optional lead score and a label. This feeds CallTrackingMetrics conversion and ROI reporting, so it directly shapes which marketing source gets credit. No action in this connector reverses it.
Contacts
6- List Contacts Lists contacts stored in the account address book, with optional free-text search across name, phone number and email, and pagination. Contacts represent the people who have called or been imported and are reused across calls, lists and campaigns.
- Get Contact Retrieves a single contact by ID, including name, phone number, email, tags and any custom fields stored on the record.
- Create Contact Creates a contact with a name, phone number, email, country code and notes, and returns the created record including its new ID. The phone number is what matches future inbound calls to this contact.
- Update Contact Updates an existing contact's details. Only supplied fields change and omitted fields keep their current values, which makes it safe to drive from a partial CRM sync.
- List Contact Lists Lists the contact lists defined in the account, meaning the segments and audiences used to group contacts for outbound campaigns and reporting. Returns each list's ID, name and contact count.
- List Contacts In List Lists the contacts belonging to a specific contact list. Find the list ID with List Contact Lists first. The API caps this page size at 10 records, so plan the paging accordingly.
Tracking Numbers and Sources
3- List Tracking Numbers Lists the tracking numbers provisioned in the account, each with its formatted display, status, routing configuration, assigned tracking source and rolling call and minute statistics. Use it to inventory numbers or to feed number selection elsewhere in a flow.
- Get Tracking Number Retrieves the full configuration of a single tracking number by ID, including its route_to routing, assigned tracking source, call settings, country code and statistics.
- List Tracking Sources Lists the tracking sources configured in the account, meaning the marketing channels such as paid search, organic or direct mail. Sources attribute inbound calls to campaigns using referrer and landing-URL rules, and this returns each source's ID, name and matching rules.
Contact Center
3- List Agents Lists the contact center agents configured in the account, with availability status and contact center settings. Agents are the people who handle inbound calls and chats.
- Get Agent Events Retrieves the timeline of contact center events for a single agent inside a time window: status changes, logins and logouts, call handling. Requires the agent's internal user ID, which comes from List Users, and start and end times in epoch seconds.
- List Users Lists the staff user accounts belonging to the account, including name, email and role, covering admins, managers and agents. This is where the internal user IDs that Get Agent Events needs come from.
Configuration and Metadata
4- List Tags Lists the tags defined in the account. Tags label calls and contacts and drive segmentation and reporting, so reading them is how a flow learns the vocabulary the team actually uses.
- List Reports Lists the saved reports configured in the account, returning each report's ID, name and configuration so it can be referenced or reviewed. This returns report definitions, not report results.
- List Webhooks Lists the outbound webhooks configured in the account, with each webhook's ID, destination URL and delivery settings. These are CallTrackingMetrics webhooks pointing at whatever endpoints your account already configured. Listing them is an audit action and creates no FlowRunner trigger.
- List Form Reactors Lists the FormReactors configured in the account, returning each one's ID and settings. FormReactors capture web-form submissions as trackable activity and can drive routing, notifications and lead follow-up on the CallTrackingMetrics side.
Frequently Asked Questions
What can FlowRunner do with CallTrackingMetrics?
FlowRunner agents can run List Accounts, List Calls, and Get Call in CallTrackingMetrics, plus 18 more actions.
Does connecting CallTrackingMetrics to FlowRunner require OAuth?
No. CallTrackingMetrics connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can CallTrackingMetrics trigger a FlowRunner workflow automatically?
CallTrackingMetrics doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with CallTrackingMetrics
$100 in credits. No card required. Connect in minutes.