Resources · Make integration

CallHippo Make integrationAutomate CallHippo with Make.

Every call and text in CallHippo can now set off the next step on its own. The CallHippo Make integration gives you 2 instant triggers and 10 actions for contacts, deals and users. This page walks sales and support teams through the connection and a first working scenario.

Try the CallHippo integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the CallHippo Make integration do for you?

The CallHippo Make integration links your CallHippo account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger or an action. CallHippo can wake that scenario up the moment a call or an SMS happens, and Make can then create, update or delete contacts, deals and users for you.

A deal after every promising call. Watch Call Activity starts the scenario when a call is logged, and Create a Deal attaches a new opportunity to the contact, so no conversation slips out of the pipeline because nobody typed it in.

A contact list that follows your other tools. When a lead arrives from a form or a spreadsheet, Create a Contact puts it in the CallHippo dialer, and Update a Contact keeps the details in step later. Pages such as the Airtable Make integration show the other side of that flow.

Seats that match your team. Create a User, Update a User and Delete a User let an onboarding or offboarding process manage CallHippo accounts without a manual ticket.

Know the limits before you build. Make's own documentation for CallHippo is thin: Make says it cannot yet publish a complete guide for this app, so field details are learned in the editor. There is no search module either, and anything the listed modules skip goes through Make an API Call. The same app often exists as an n8n node too; the n8n vs Make comparison lays out how the two tools differ, and the Make review helps if you are still choosing.

Connect

How do you connect CallHippo to Make?

  1. 01

    Add a CallHippo module

    In your scenario, click the + and type CallHippo, then pick any of its modules. Make asks for a connection the first time: that is your CallHippo account linked to Make once, and every CallHippo module reuses it. Click Create a connection.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps when you manage several CallHippo accounts, for example one for sales and one for support. Pick something you will recognize later in the connection list.

  3. 03

    Authorize and save

    Depending on what CallHippo offers, either approve Make on the CallHippo page that opens, or paste the key CallHippo gives you into the field. Then click Save. The module now shows the connection and you can fill in its fields.

First scenario

Your first scenario with CallHippo

GoalWhen a call is logged in CallHippo, Make opens a deal on that contact.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario. An empty canvas appears with a large + in the middle: that is where the first module goes.

  2. 02

    Add the call trigger

    Click the +, search for CallHippo and choose Watch Call Activity. Select the connection you created, or click Create a connection if you skipped that part.

  3. 03

    Add the deal action

    Click the + on the right of the trigger and pick Create a Deal. Fill its fields by mapping data from the call bundle, the item the trigger passes along for each call. Run once shows which call details you can use for the contact.

  4. 04

    Test with Run once

    Click Run once, then place or receive a test call in CallHippo. Open the bubbles above each module to read the bundles they got and check the deal in CallHippo.

  5. 05

    Switch it on

    When the test looks right, switch the scenario on. Because the trigger is instant, CallHippo alerts Make on each call instead of waiting for a schedule.

Triggers

What starts a CallHippo scenario

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

CallHippo1Watch Call Activity

Watch Call Activity

Instant trigger

In Make“Triggers when there is a call activity.”

This trigger turns every call activity in CallHippo into a fresh start for your scenario, so follow-up work begins while the conversation is still fresh in the rep's mind. Each call arrives in Make as one bundle you can pass to the next module.

How it fires
instant: CallHippo calls Make through a webhook as soon as the activity happens, which is why the module carries the lightning badge.
When to use it
pick it when a phone conversation should create or update something elsewhere, such as a deal, a CRM note or a message to a manager.
Watch out
every call that reaches the scenario uses operations, the unit Make counts on your plan, so keep in mind that busy phone lines mean more operations.
CallHippo2Watch SMS Activity

Watch SMS Activity

Instant trigger

In Make“Triggers when there is an SMS activity.”

Text messages get their own trigger: Watch SMS Activity hands Make each SMS activity from CallHippo, which lets a written exchange with a customer feed your tools as reliably as a call does.

How it fires
instant: CallHippo notifies Make through a webhook the moment the SMS activity occurs, with no schedule to set.
When to use it
choose it when your team confirms appointments or answers questions by text and wants those exchanges logged or routed to the right person.
Watch out
it covers SMS only; for calls, build a second scenario on Watch Call Activity rather than expecting one trigger to catch both.
Modules

What Make can do in CallHippo

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

CallHippo1

Create a Contact

Action

In Make“Creates a contact in CallHippo dialer.”

New leads land in the CallHippo dialer without anyone copying names and numbers by hand, so reps can call them straight away from the app they already use.

When to use it
right after a web form, a spreadsheet row or another CRM produces a new person to call.
Watch out
there is no search module to check for an existing record first, so a lead sent twice can become two contacts.
CallHippo2

Create a Deal

Action

In Make“Creates a deal in specified contact.”

Opening an opportunity becomes automatic: this action adds a deal to a contact you specify, so the sales pipeline in CallHippo reflects conversations as they happen.

When to use it
after Watch Call Activity, or when a quote request in another tool means money is now on the table.
Watch out
the deal belongs to a contact, so make sure that contact exists before this module runs.
CallHippo3

Create a User

Action

In Make“Creates a user in users CallHippo account.”

Your onboarding flow can hand each new colleague a CallHippo seat. Nobody has to remember to ask an admin for it.

When to use it
when a hire is confirmed in your HR tool or an onboarding sheet and that person will make or take calls.
Watch out
the user lands in your live CallHippo account, so run the scenario with Run once on a test hire before you switch it on.
CallHippo4

Delete a Contact

Action

In Make“Deletes a contact from CallHippo dialer.”

Removing a contact from the dialer keeps reps from calling someone who asked to be left alone or who is no longer a lead.

When to use it
when an opt-out, an unsubscribe or a closed account in another system should clear the person from CallHippo too.
Watch out
no CallHippo module in Make brings a deleted contact back, so test it with Run once on a dummy contact before switching the scenario on.
CallHippo5

Delete a Deal

Action

In Make“Deletes a deal of contact from CallHippo dialer.”

Stale or duplicate opportunities disappear from a contact's record, leaving a pipeline your team can actually trust when they plan calls.

When to use it
when a deal is cancelled or merged elsewhere and CallHippo should stop showing it.
Watch out
pick this over Update a Deal only when the history really has no value, because no module restores a deleted deal.
CallHippo6

Delete a User

Action

In Make“Deletes a user from CallHippo account.”

Offboarding closes the phone access too: this action removes a person from your CallHippo account as soon as your process says they have left.

When to use it
at the end of an offboarding checklist, triggered by the departure record in your HR or IT tool.
Watch out
the module acts on whatever user you map, so check it points to the person who actually left.
CallHippo7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the other nine actions leave out can still be reached: this module calls any endpoint of the CallHippo API with the connection you already set up.

When to use it
when you need a request the listed modules do not offer, such as a lookup, since the app has no search module.
Watch out
you write the request yourself, and Make's own CallHippo documentation is limited, so expect some trial with Run once.
CallHippo8

Update a Contact

Action

In Make“Updates specified contact in CallHippo dialer.”

Contact details in CallHippo stay current when they change somewhere else, so the name and number on a rep's screen match what your CRM knows.

When to use it
when a customer edits their profile, changes company or gets a new owner in your main database.
Watch out
the module needs to know which contact to change, so keep its CallHippo reference stored in the source tool.
CallHippo9

Update a Deal

Action

In Make“Updates a deal of specified contact in CallHippo dialer.”

A deal moves forward on its own when something happens elsewhere, so the CallHippo record never lags behind the real state of the sale.

When to use it
after a signed quote, a payment or a second call changes where the opportunity stands.
Watch out
it edits a deal of a specified contact, so you need both references at hand, and a wrong mapping overwrites the wrong opportunity.
CallHippo10

Update a User

Action

In Make“Updates a specific user in CallHippo account.”

Changes in your team show up in CallHippo without an admin reopening the settings, whether someone switches department or changes name.

When to use it
when your directory or HR tool records a role or team change for a colleague who uses CallHippo.
Watch out
prefer it over a Delete a User followed by a Create a User, which turns a simple change into two operations and a new account.
Need help

Need help automating CallHippo with Make?

A person reads every message.

FAQ

CallHippo and Make: common questions

01Is the CallHippo Make integration free?
Yes, on Make's side. CallHippo is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios no more often than every 15 minutes, stops an execution after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, lift the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations per month. You still need your own CallHippo account, which Make does not include.
02What do you need to connect CallHippo to Make?
A CallHippo account and a Make account are enough to begin. Make's documentation for CallHippo lists no specific prerequisite and no official connection steps, so the generic flow applies: add a CallHippo module, click Create a connection, give it a name if you like, then authorize Make on the CallHippo page or paste the key CallHippo provides, and click Save. The connection is stored once and reused by all 12 CallHippo modules, so you only go through this the first time.
03Do CallHippo triggers in Make fire in real time?
Yes. Both CallHippo triggers, Watch Call Activity and Watch SMS Activity, are instant. That means CallHippo calls Make through a webhook as soon as a call or an SMS activity happens, and the scenario starts right away instead of waiting for its schedule. In the editor you can spot them by the lightning badge on the module. The 15 minute default schedule of new scenarios only applies to scheduled triggers, which this app does not have. Each event still counts as operations on your Make plan.
04What if a CallHippo module is missing in Make?
It depends on what you need, but Make an API Call usually covers it. The listed modules create, update and delete contacts, deals and users, and there is no search module. When you need anything else from the CallHippo API, Make an API Call reaches any endpoint with the same connection. Keep in mind that Make says its CallHippo documentation is incomplete because public information about the app is limited, so plan a few Run once tests while you learn the fields.
05Should you use Make or n8n for CallHippo?
It depends on the tool your team already works in. On Make, CallHippo comes with 12 ready modules, including 2 instant triggers, and Make an API Call for the rest. The same app often has an n8n node as well, so check which tool offers the actions your process needs before choosing. If your other automations already run in Make, keeping CallHippo there means one place to watch, test and fix. The comparison page linked above goes through the differences in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations