Resources · Make integration

CallTrackingMetrics Make integrationAutomate CallTrackingMetrics with Make.

What if every call tracked in CallTrackingMetrics started its own follow-up? The CallTrackingMetrics Make integration gives you 30 modules, with 5 instant triggers. This guide shows marketing and sales teams how to link the account and build a first scenario.

Try the CallTrackingMetrics integration on MakeSee the 30 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the CallTrackingMetrics Make integration automate?

The CallTrackingMetrics Make integration links your call tracking account to Make, a visual tool where you chain apps without writing code. You build a scenario (the automation itself) out of modules, and each module either listens for a call, acts on your account or searches it.

Text back every caller. Start from Watch Call Ended, then add Send SMS Message: the caller gets a short follow-up right after hanging up, and nobody on the team has to remember it.

Keep consent lists clean. When someone asks to stop hearing from you in a form or a helpdesk app, Add to Do Not Call List and Add Opt Out Text/SMS record the request in CallTrackingMetrics, so the next campaign respects it.

Close the loop on revenue. When a deal is won in your CRM, Search Activities by Phone Number finds the matching call and Create/Edit Sale Record attaches the sale to it. Your attribution reports then show which source brought paying customers.

Two honest limits. The Make documentation for this app is marked as AI-generated and asks you to verify important details, and its action and search modules ship without a description. Test each one with Run once before trusting it, and keep the Make troubleshooting guide nearby. If you are new to the editor, Make training covers the basics. Weighing another tool? n8n vs Make puts both side by side.

Connect

How do you connect CallTrackingMetrics to Make?

  1. 01

    Copy your API credentials

    You need an active CallTrackingMetrics account and an API key. Log in, open the account settings or integrations area, find the section for API credentials, then copy the Client ID, the Client secret and the Server value when it is shown.

  2. 02

    Add a module and start the connection

    In Make, add any CallTrackingMetrics module to your scenario and click Create a connection. A connection is your account linked once, then reused by every CallTrackingMetrics module you add later.

  3. 03

    Name it and paste the keys

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the credentials you copied, or follow the instructions on screen, and save.

First scenario

Your first scenario: a text after every call

GoalWhen a call ends in CallTrackingMetrics, Make sends a follow-up SMS through your account.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. This first slot holds the trigger, the module that decides when everything starts.

  2. 02

    Add Watch Call Ended

    Search for CallTrackingMetrics and pick Watch Call Ended. Click Create a webhook, then Create a connection, and paste the API credentials from your account.

  3. 03

    Add Send SMS Message

    Click the + to the right of the trigger and choose Send SMS Message. Fill its fields and map the caller details the trigger received, so each text goes to the right person.

  4. 04

    Test with Run once

    Click Run once, then end a test call on a tracked number. Open the bubbles above each module to read the bundles, the items Make passed along, and check the text went out.

  5. 05

    Switch it on

    The trigger is instant, so the scenario runs whenever CallTrackingMetrics calls Make instead of waiting for a schedule. Save, switch the scenario on, and each ended call now gets its follow-up.

Triggers

What can start a CallTrackingMetrics scenario?

5 modules start a scenario when something happens in CallTrackingMetrics. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by CallTrackingMetrics as soon as it happens.

CallTrackingMetrics1Watch Call/Activity Started

Watch Call/Activity Started

Instant trigger

In Make“Triggers when an inbound phone call/activity starts.”

Your scenario starts the moment an inbound call or another activity begins in CallTrackingMetrics, so the next move happens while the conversation is still live. Each new activity reaches Make as one bundle, the single item passed on to the next module.

How it fires
instant, CallTrackingMetrics calls Make through a webhook as soon as the activity starts, which is what the lightning badge on the module means.
When to use it
a sales rep should get a heads-up in another tool while the phone is still ringing.
Watch out
the call is not over yet at this point, so anything that depends on how it went belongs on Watch Call Ended.
CallTrackingMetrics2Watch Call Ended

Watch Call Ended

Instant trigger

In Make“Triggers when the call ends.”

As soon as a caller hangs up, this trigger hands the finished call to your scenario. That makes it the natural starting point for follow-ups, logging and anything that should react to a completed conversation, one bundle per call.

How it fires
instant, CallTrackingMetrics calls Make through a webhook as soon as the call ends; nothing waits on a schedule.
When to use it
a thank-you text or a CRM update should go out right after the conversation.
Watch out
if a value you map comes back empty in the Run once test, compare with Watch Call Ended (Delayed), which fires later.
CallTrackingMetrics3Watch Call Ended (Delayed)

Watch Call Ended (Delayed)

Instant trigger

In Make“Triggers 1 hour after call data is captured.”

This variant holds back before waking your scenario: CallTrackingMetrics sends the call one hour after its data is captured. You give up speed and get a later snapshot of the call in return, which suits work where nobody is waiting on the other end.

How it fires
instant, CallTrackingMetrics calls Make through a webhook, one hour after capture rather than at hang-up.
When to use it
a reporting or lead scoring scenario, where a same-minute reaction brings nothing.
Watch out
never pair it with a customer text meant to feel immediate, the one-hour gap is part of the trigger.
CallTrackingMetrics4Watch Call Events

Watch Call Events

Instant trigger

In Make“Triggers when a call event has occurred.”

Broader than the other watchers, this one reacts whenever a call event occurs in CallTrackingMetrics. A single scenario can then follow what happens across your calls instead of one moment only.

How it fires
instant, CallTrackingMetrics calls Make through a webhook as soon as the event happens.
When to use it
you want one entry point for call activity and plan to decide later in the scenario what each event should do.
Watch out
the module listing does not say which events count, so click Run once, place a test call and read the bundles before mapping anything.
CallTrackingMetrics5Watch Session Associated to the Activity Record

Watch Session Associated to the Activity Record

Instant trigger

In Make“Triggers when a session data is associated to the activity record.”

Here the scenario starts when session data gets attached to an activity record in CallTrackingMetrics. It is the attribution moment: CallTrackingMetrics presents itself as the way to trace each inbound call back to its source, and this trigger tells Make when that link exists.

How it fires
instant, CallTrackingMetrics calls Make through a webhook as soon as the session is associated.
When to use it
a marketing dashboard or ad tool should learn which visit produced a call.
Watch out
the doc does not say when this fires compared with the end of the call, so keep follow-up texts on the call triggers and use this one for source data.
Modules

What CallTrackingMetrics can do inside a scenario

CallTrackingMetrics gives you 25 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

CallTrackingMetrics1

Add Contact

ActionIn the docs only

New people land in your CallTrackingMetrics contacts without anyone typing them in. The module creates a contact from data another app already holds, like a form entry or a CRM record.

When to use it
a lead fills a web form and you want the name ready before they ever call.
Watch out
run it once on a test lead first, because repeated form submissions can create repeated contacts.
CallTrackingMetrics2

Add Numbers

ActionIn the docs only

Phone numbers get pushed into CallTrackingMetrics straight from your scenario, which saves copying lists by hand. The module has no official description, so open it after connecting and look at what Make proposes to fill.

When to use it
a spreadsheet or CRM holds numbers that CallTrackingMetrics needs to know about.
Watch out
its twin Remove Numbers undoes the job, so name both modules clearly in the scenario.
CallTrackingMetrics3

Add Opt Out Text/SMS

ActionIn the docs only

Someone who asked for no more texts gets flagged as opted out in CallTrackingMetrics, and your messaging stays compliant without a manual list. It is the consent side of Send SMS Message.

When to use it
a contact unsubscribes in a form, a helpdesk ticket or a reply, and the request must reach your texting account.
Watch out
only Remove Opt Out Text/SMS reverses it, keep that module for explicit new consent.
CallTrackingMetrics4

Add to Do Not Call List

ActionIn the docs only

A number goes on your do not call list in CallTrackingMetrics the moment the request comes in, so the team stops dialing it. That protects your outreach from calling people who said no.

When to use it
a prospect marks "do not contact" in your CRM and the dialer must follow.
Watch out
this covers calls, while texts have their own module, Add Opt Out Text/SMS, so add both when a person refuses everything.
CallTrackingMetrics5

Create a Webhook

ActionIn the docs only

From inside a scenario, this action sets up a webhook in your CallTrackingMetrics account, a web address the account calls when something happens. Handy when you manage several accounts and want the same setup everywhere.

When to use it
an onboarding scenario prepares a new client account in one pass.
Watch out
it is not the Create a webhook button of the instant triggers; for a simple trigger, that button is enough.
CallTrackingMetrics6

Create/Edit Sale Record

ActionIn the docs only

Revenue gets tied back to the call that brought it: the module creates a sale record in CallTrackingMetrics or edits one that exists. Your attribution then counts money, not only rings.

When to use it
a deal is marked won in your CRM or an order is paid in your store.
Watch out
it has to know which call to update, so place Search Activities by Phone Number before it and map the result.
CallTrackingMetrics7

Delete a Contact

ActionIn the docs only

Removes a contact from CallTrackingMetrics, which keeps the account tidy when someone asks to be erased or a duplicate slipped in. One bundle in, one contact gone.

When to use it
a data deletion request is approved in another tool and must reach every system.
Watch out
a delete cannot be taken back from Make, so test it on a dummy contact with Run once before switching the scenario on.
CallTrackingMetrics8

Formreactor Server Side Request

ActionIn the docs only

Sends a FormReactor request from the server side, so a form you collect somewhere else can still reach CallTrackingMetrics and be handled like its own forms. No official description comes with it, so read the fields Make shows once connected.

When to use it
leads arrive through a form tool that CallTrackingMetrics does not host.
Watch out
check the result in your account after Run once before sending real leads through it.
CallTrackingMetrics9

Get Activity Details

ActionIn the docs only

Pulls the full details of one activity, a call or a text, when your scenario only knows which one it is. The later modules can then map everything the account holds about it.

When to use it
a trigger or a search gave you an activity, and you need more than it carried.
Watch out
it reads a single activity; to collect several, List Activities or one of the search modules fits better.
CallTrackingMetrics10

List Activities

SearchIn the docs only

Returns activities from your account as separate bundles, one per call or text. Each bundle runs through the rest of the scenario, which turns a pile of calls into rows you can export or score.

When to use it
a report in a spreadsheet should hold every recent activity.
Watch out
every bundle costs an operation, one run of one module, in each following module, so a long list uses up your plan faster.
CallTrackingMetrics11

List Tracking Numbers

SearchIn the docs only

Gives you the tracking numbers of the account as bundles, useful for an inventory you can share with people who never log into CallTrackingMetrics.

When to use it
a marketing sheet should show which numbers exist before a new campaign gets one.
Watch out
it lists everything; when you only need a few numbers, Search Tracking Numbers returns a smaller set and costs fewer operations.
CallTrackingMetrics12

Make an API Call

ActionIn the docs only

Reaches any endpoint of the CallTrackingMetrics API with the connection you already set up, which covers what the other modules leave out. No second login, no separate key to paste.

When to use it
you need an operation of CallTrackingMetrics that none of the named modules offers.
Watch out
you write the request yourself from the vendor API documentation, so start with Run once and read the response before wiring the next module.
CallTrackingMetrics13

Modify Activity Details

ActionIn the docs only

Updates an activity that already exists in CallTrackingMetrics, so what your team learns after the call ends up on the call itself. The record stays the single place to look.

When to use it
a rep qualifies the lead in the CRM and the call should reflect that outcome.
Watch out
you need the right activity first, so pair it with Search Activities by Phone Number or a call trigger.
CallTrackingMetrics14

Purchase Tracking Number

ActionIn the docs only

Buys a new tracking number for your account straight from a scenario, so a campaign can get its own line the moment it is approved.

When to use it
a new ad campaign or location is created in your project tool and needs a number to measure it.
Watch out
a purchase goes through your CallTrackingMetrics account, so check what your subscription allows before it runs without supervision, and test it only once.
CallTrackingMetrics15

Redact Activity Details

ActionIn the docs only

Hides details of an activity in CallTrackingMetrics, which helps when a call or text captured something that should not stay readable. The request reaches the account without anyone digging through recordings.

When to use it
a privacy request is logged and the matching call has to be cleaned up.
Watch out
no official description says what gets hidden, so run it on a test activity and look at the result in your account.
CallTrackingMetrics16

Release a Tracking Number

ActionIn the docs only

Gives a tracking number back once its campaign is over, so the account only keeps the lines you still use.

When to use it
a campaign is archived in your planning tool and its number has no reason to stay.
Watch out
releasing a number means letting it go, so map the number carefully and confirm it with List Tracking Numbers first.
CallTrackingMetrics17

Remove From Do Not Call List

ActionIn the docs only

Takes a number off your do not call list in CallTrackingMetrics, so the team can dial it again after the person gives new consent.

When to use it
a contact opts back in through a signed form or a preference center.
Watch out
run it only on a clear, recorded consent event, because the whole point of the list is that nobody removes numbers by accident; texts need Remove Opt Out Text/SMS as well.
CallTrackingMetrics18

Remove Numbers

ActionIn the docs only

Clears numbers you no longer want in CallTrackingMetrics, the reverse of Add Numbers. The list the account holds stays in step with the source you manage elsewhere.

When to use it
a row is deleted in your master spreadsheet and the account should forget the number too.
Watch out
the doc does not describe what removing does to past data, so test on a spare number before running it on real ones.
CallTrackingMetrics19

Remove Opt Out Text/SMS

ActionIn the docs only

Lifts an SMS opt out in CallTrackingMetrics, so a person who agreed again can receive your texts.

When to use it
a customer ticks the SMS consent box on a new order or form after refusing earlier.
Watch out
tie it to an explicit yes and nothing else; if the same scenario also calls Send SMS Message, place this module before it.
CallTrackingMetrics20

Search Activities by Custom Fields

SearchIn the docs only

Finds the activities whose custom fields match what you look for, and returns zero, one or several bundles. It uses the labels your team already adds in CallTrackingMetrics.

When to use it
calls are tagged with a campaign or a deal stage and you want only those.
Watch out
a search can come back empty, so read the Run once output before blaming the next module.
CallTrackingMetrics21

Search Activities by Phone Number

SearchIn the docs only

Looks up every activity linked to one phone number, which gives your scenario the call history of a person in one step.

When to use it
a deal closes in the CRM and you need the calls of that customer to record a sale or update details.
Watch out
one number can match several calls, each one a bundle; decide whether the following modules should run on all of them.
CallTrackingMetrics22

Search Tracking Numbers

SearchIn the docs only

Narrows your tracking numbers down to the ones that match your search, instead of pulling the whole list.

When to use it
before releasing or reusing a number, a scenario checks that it exists and grabs its details.
Watch out
a search can return no match, several matches or exactly the one you expect; test with Run once and read what came back before chaining Release a Tracking Number.
CallTrackingMetrics23

Send SMS Message

ActionIn the docs only

Sends a text from your CallTrackingMetrics account, so follow-ups, reminders and confirmations leave from the same place your calls are tracked.

When to use it
right after Watch Call Ended, or when a form submission deserves a quick reply.
Watch out
people who opted out should not receive anything, so keep Add Opt Out Text/SMS in the same setup and respect it.
CallTrackingMetrics24

Start a Dialer

ActionIn the docs only

Launches a dialer in CallTrackingMetrics from your scenario, so an outbound session can begin when the right event happens instead of when someone remembers.

When to use it
a fresh batch of leads is ready in your CRM and the call team should start on it.
Watch out
clean the batch first with the do not call list modules, and plan the matching Stop a Dialer event before you switch the scenario on.
CallTrackingMetrics25

Stop a Dialer

ActionIn the docs only

Halts a running dialer in CallTrackingMetrics, the natural partner of Start a Dialer, so outbound calling ends on a clear signal.

When to use it
a campaign closes in your planning tool, or a quota of booked meetings is reached in the CRM.
Watch out
it needs to target the same dialer your start module launched, so map that value from the earlier run instead of typing it.
Need help

Need help automating CallTrackingMetrics with Make?

A person reads every message.

FAQ

Questions about the CallTrackingMetrics Make integration

01Is the CallTrackingMetrics Make integration free?
Yes, on the Make side. CallTrackingMetrics is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run. You still need an active CallTrackingMetrics account with its own subscription.
02What do you need to connect CallTrackingMetrics to Make?
An active CallTrackingMetrics account and an API key. In the account settings or integrations area, find the API credentials section and copy the Client ID, the Client secret and the Server value if it appears. In Make, add a CallTrackingMetrics module, click Create a connection, optionally give it a name, and paste those values. For an instant trigger, click Create a webhook first. The connection is then reused by every module of the app.
03Do CallTrackingMetrics triggers in Make react in real time?
Yes. All five triggers are instant: CallTrackingMetrics calls Make through a webhook as soon as the event happens, so the scenario does not wait for a schedule. One exception by design, Watch Call Ended (Delayed) fires one hour after the call data is captured. Pick Watch Call/Activity Started for a reaction during the call, Watch Call Ended right after it, and Watch Session Associated to the Activity Record when the source of the call matters.
04What if a CallTrackingMetrics module is missing in Make?
Use Make an API Call. The app includes this module, which reaches any endpoint of the CallTrackingMetrics API with the connection you already have, so nothing new to authorize. You write the request from the vendor API documentation. Keep in mind that the Make documentation for this app is flagged as AI-generated and asks you to verify important information, so test every call with Run once and contact CallTrackingMetrics if something in their documentation looks off.
05Should you use Make or n8n with CallTrackingMetrics?
It depends on what you check. On Make, CallTrackingMetrics comes with 30 ready modules, 5 of them instant triggers, and runs from the Free plan. Many apps also have an n8n node, so look at what n8n offers for this one before choosing, then compare the modules each tool gives you for your exact use case. Neither answer is universal: pick the tool your team will keep maintaining, and read the n8n vs Make comparison on this site for the broader criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations