Resources · Make integration

CallRail Make integrationAutomate CallRail with Make.

Every call and text CallRail tracks can start an automation. The CallRail Make integration gives you 9 modules: 8 triggers and one API call. This page shows marketers and ops leads how to link the account and run a first scenario.

Try the CallRail integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the CallRail Make integration do?

The CallRail Make integration links your CallRail account to Make, a tool where you build a scenario (an automation made of modules, each one a brick such as a trigger or an action). CallRail events, like a new call or an incoming text, start the scenario and hand their data to the next module.

A call log nobody types by hand. Watch Calls fires as soon as an inbound call lands, and again when that call changes after it ends. Each call arrives in Make as a bundle (one item passed from module to module), ready for the next app in the scenario.

Texts that reach the right person. Watch SMS Received and Watch SMS Sent follow your text conversations, so a reply from a prospect can open a task or alert a teammate instead of sitting unread in CallRail.

An account that stays tidy. Watch Companies, Watch Trackers and Watch Users notice new records on the admin side, which helps when an agency adds a client company or a new tracking number goes live.

What the integration does not do: it has no module to create or edit records in CallRail. For that, Make an API Call reaches any endpoint of the CallRail API with the same connection. If you also weigh n8n, which often has a node for the same app, the n8n vs Make comparison helps you pick. Before you start, the Make pricing page explains how plans count usage, and Make training covers the editor from zero.

Connect

How do you connect CallRail to Make?

  1. 01

    Get your API key and account ID

    In CallRail, open the Integrations icon in the left bar, then API Keys (or Data Access). Click Create New API v3 Key and copy the key. Your account ID is the nine digit number after /a in the dashboard URL.

  2. 02

    Add a CallRail module in Make

    In your scenario, add any CallRail module and click Create a connection. A connection is your CallRail account linked to Make once, then reused by every CallRail module. The Connection name field is optional.

  3. 03

    Paste your credentials and save

    Enter the API key and the account ID you copied, then follow the on-screen prompts. On a module tagged instant, Make first asks you to click Create a webhook, and only then Create a connection.

First scenario

Your first scenario with CallRail

GoalWhen an inbound call reaches CallRail, Make receives it and sends a request of your choice to the CallRail API.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place the first module. Search for CallRail and pick Watch Calls.

  2. 02

    Create the webhook and connection

    Watch Calls is instant, so click Create a webhook, then Create a connection and paste your API key and account ID. CallRail will now call Make whenever a call comes in.

  3. 03

    Add the API call

    Click the + on the right of Watch Calls and add Make an API Call. Pick the CallRail endpoint you need and map data from the call bundle into the request.

  4. 04

    Test with Run once

    Click Run once, then place a test call to one of your tracking numbers. Open the bubbles on each module to read the bundles they received and check the request went through.

  5. 05

    Switch the scenario on

    Once the test looks right, turn the scenario on. Since the first module is instant, it runs each time CallRail reports a call, with no schedule to set on the clock.

Triggers

What can start a CallRail scenario?

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

CallRail1Watch Calls

Watch Calls

Instant trigger

In Make“Triggers when an inbound phone call is received or a call has changed after it's ended.”

You get every inbound call in Make the moment CallRail receives it, plus a second pass when that call is updated after it ends. It is the broadest call trigger of the app.

How it fires
instant, CallRail calls Make through a webhook as soon as it happens.
When to use it
you want one scenario that logs the call and then reacts again once the call record is complete.
Watch out
the description covers two moments, the call received and the call changed after it ends, so test both before you map fields.
CallRail2Watch Companies

Watch Companies

Scheduled trigger

In Make“Triggers when a new company is created.”

Each new company created in your CallRail account shows up in Make as its own bundle, so a fresh client setup can kick off the rest of your onboarding without anyone copying names across tools.

How it fires
scheduled, Make checks CallRail on the scenario's schedule.
When to use it
an agency adds a client company in CallRail and wants the matching folder or record created elsewhere.
Watch out
nothing happens between two checks; a new scenario checks every 15 minutes by default, and the Free plan cannot go lower.
CallRail3Watch Modified Call

Watch Modified Call

Instant trigger

In Make“Triggers when a call has changed after it’s ended.”

This one waits until a call has ended and something in it changes, then hands you the updated call. You work with the finished record instead of the first raw version.

How it fires
instant, CallRail calls Make through a webhook as soon as the change happens.
When to use it
your team edits calls after the fact and the downstream app should only see the corrected data.
Watch out
it only fires once the call has ended; to react the moment a call comes in, pick Watch Pre-Call.
CallRail4Watch Pre-Call

Watch Pre-Call

Instant trigger

In Make“Triggers when an inbound phone call is received by CallRail.”

Your scenario starts as soon as CallRail receives an inbound call, which makes it the earliest point you can react to a caller. Speed is the whole point of this module.

How it fires
instant, CallRail warns Make through a webhook the moment the call arrives.
When to use it
a sales rep should get an alert about a new caller while the conversation is still fresh.
Watch out
it fires on receipt of the call; for changes made once the call has ended, add Watch Modified Call instead.
CallRail5Watch SMS Received

Watch SMS Received

Instant trigger

In Make“Triggers when an SMS message is received.”

Incoming text messages land in Make one by one, so a prospect who replies by SMS gets noticed even when nobody has CallRail open.

How it fires
instant, CallRail pushes the message to Make through a webhook when it arrives.
When to use it
a lead texts back after a missed call and a teammate needs to see it in the chat tool the team already reads.
Watch out
it only covers messages you receive; outgoing texts need Watch SMS Sent in a separate scenario.
CallRail6Watch SMS Sent

Watch SMS Sent

Instant trigger

In Make“Triggers when an SMS message is sent.”

Every text your team sends from CallRail reaches Make, which gives you a record of outbound follow-ups without asking anyone to report them.

How it fires
instant, CallRail notifies Make through a webhook when the message goes out.
When to use it
a manager wants each follow-up text added to the contact history in another tool.
Watch out
pair it with Watch SMS Received if you need both sides of the conversation, since each trigger sees only one direction.
CallRail7Watch Trackers

Watch Trackers

Scheduled trigger

In Make“Triggers when a new tracker is created.”

When someone creates a new tracker in CallRail, Make picks it up so the rest of your setup knows a new number is live and can be tied to its campaign.

How it fires
scheduled, Make checks CallRail on the scenario's schedule.
When to use it
a marketer launches a campaign with its own tracker and wants it listed in a shared sheet for the team.
Watch out
since it polls, a tracker created just after a check waits for the next run before it appears.
CallRail8Watch Users

Watch Users

Scheduled trigger

In Make“Triggers when a new user is created.”

New users added to your CallRail account come through to Make, which helps you keep access lists and internal directories in step with the people who can see your call data.

How it fires
scheduled, Make checks CallRail on the scenario's schedule.
When to use it
an ops lead wants a notice every time a colleague or a client contact is given a CallRail login.
Watch out
the scenario's schedule decides when new users appear, and Make counts each operation (one run of a module on one bundle) on your plan.
Modules

What else can Make do in CallRail?

CallRail gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

CallRail1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you can reach any endpoint of the CallRail API from your scenario, using the connection you already set up. It fills the gap left by the triggers, since the app has no ready-made action module.

When to use it
you need to write or read something in CallRail that none of the eight triggers covers.
Watch out
you pick the endpoint and build the request yourself, so keep the CallRail API documentation open next to Make.
Need help

Need help automating CallRail with Make?

A person reads every message.

FAQ

CallRail and Make: common questions

01Is the CallRail Make integration free?
Yes, on the Make side. CallRail is a standard app, so it works on the Free plan, which allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, and caps each run at 5 minutes. Paid plans lower the interval to 1 minute and remove the limit on active scenarios. You still need an active CallRail account with API access, and CallRail's own subscription is separate from Make.
02What do you need to connect CallRail to Make?
An active CallRail account, an API v3 key and your account ID. You create the key in CallRail under Integrations, then API Keys or Data Access, with the Create New API v3 Key button. The account ID is the nine digit number after the slash and the letter a in your dashboard URL. In Make, add a CallRail module, click Create a connection and paste both values. If a module is tagged instant, Make asks you to create a webhook first.
03Does the CallRail trigger react in real time?
It depends on the trigger. Five are instant: Watch Calls, Watch Modified Call, Watch Pre-Call, Watch SMS Received and Watch SMS Sent. CallRail calls Make through a webhook as soon as the event happens. The other three, Watch Companies, Watch Trackers and Watch Users, are scheduled: Make checks CallRail on the scenario's schedule, every 15 minutes by default. In practice, a call or text reaches your scenario right away, while a new company, tracker or user waits for the next scheduled check. The Free plan cannot check more often than that.
04What if a CallRail module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the CallRail API with the connection you already have, which is how you cover anything the eight triggers do not, such as writing data back into CallRail. The Make help page for this app also warns that its text is AI-generated from CallRail's documentation, so check important details with CallRail before you rely on them. Keep in mind that you build each request yourself.
05Should you use Make or n8n for CallRail?
It depends on the tool your team already works in. n8n often has a node for the same app, so check whether it covers CallRail the way you need. On Make, you get eight named CallRail triggers, five of them instant, plus Make an API Call for the rest, all in a visual editor. Compare the triggers each tool offers for CallRail against the events you actually need before you choose.
Same platform

Other docs you might need on this stack.

Browse all integrations