CallHippo

Manage users, contacts, call logs, and dialler campaigns on the CallHippo cloud phone system. Agents provision seats, log call activity against the right record, and keep outbound campaigns supplied with contacts.

21 actions API key available

CallHippo website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

The HR system marks an employee's last working day as reached

Agent resolves the person's CallHippo account with List Users and reads their numbers and teams with Get User

Agent calls Update User Call Session to close their session so calls stop ringing an unattended device

Agent pulls their recent activity from List Call Logs and List SMS Logs for the retention window

Agent posts the seat, the numbers assigned to it, the open call volume and the billing impact

The operations owner decides whether the seat is deleted or held, and only a confirmed decision reaches Delete User

What This Integration Enables

CallHippo is a cloud phone system, not a voice agent, and the connector is honest about what that means. Nothing here writes a script or synthesises a voice. What it does is administer the phone system that a human sales or support team actually works on: the seats, the teams, the numbers, the contact book, the call and SMS history, the do not call list, and the outbound dialler campaigns. It is the system of record for who called whom, and treating it that way is more useful than pretending it is something else.

Two facts shape how flows are built against it. First, CallHippo publishes no webhooks, so this connector has no triggers. Work starts from a schedule or from a change in another system, and call and SMS history is read by polling List Call Logs and List SMS Logs for a date range. Second, the operations that matter most are administrative rather than conversational: opening and closing agent sessions on a shift schedule, adding a number to the do not call list the moment somebody asks, starting and stopping dialler campaigns so they stay inside approved calling hours, and deprovisioning a seat when a person leaves. Those are exactly the tasks that get skipped when a human has to remember them, and exactly the tasks where getting one wrong is expensive.

Without FlowRunner

Seats outlive people A departed rep's seat keeps billing until someone notices it on the invoice

Calls ring nobody Numbers stay routed to a device that has already been handed back

Opt-outs travel by hand A do not call request in the CRM reaches the phone system whenever someone gets to it

With FlowRunner

Offboarding is a step in the flow The HR record change starts the deprovisioning work the same day

Routing closes with the shift Sessions open and close on schedule so calls only ring someone who is there

Opt-outs land immediately A request recorded anywhere adds the number to the do not call list right away

Use Case Scenarios

Offboarding a rep without losing the record

An employee's last day passes and the HR system updates their record. The agent resolves their CallHippo account with List Users, reads Get User to see which numbers and teams are assigned to them, and immediately calls Update User Call Session to close their session so nothing rings a device nobody is carrying. It then pulls their call and SMS history for the retention window and archives it, because deleting the seat later will make that history harder to attribute. It posts the full picture to the operations owner and stops there. The account keeps billing for one more day rather than the connector making a decision with a billing consequence on its own.

Opt-outs honoured the moment they are recorded

A customer replies "stop" to a marketing message, or a support agent ticks the do not contact box on their record. The agent calls Add Do Not Call Number so CallHippo blocks the number in both directions, then calls Delete Contact to remove them from the address book, and writes the timestamp and source of the request back to the CRM. The compliance step and its evidence happen in the same flow, which is what an auditor wants to see.

Campaigns held inside approved calling hours

A dialler campaign should only run between 9am and 6pm in the region it targets. A scheduled flow calls Control Campaign to start it at the top of the window and stop it at the close, and reads List Campaigns and List Campaign Contacts to report progress, attempt counts and the action taken on each lead. If a compliance check fails partway through, for example a batch of numbers turns out to include a jurisdiction the campaign is not cleared for, the agent stops the campaign immediately and escalates rather than letting it finish the queue.

Nightly activity sync

Because CallHippo has no webhooks, a nightly flow polls List Call Logs and List SMS Logs for the previous day, summarises each recording, and writes the activity onto the matching record in HubSpot. Calls that cannot be matched to a record are collected as automation exceptions for someone to resolve, rather than being dropped silently.

Human-in-Loop Highlight

The gate is Delete User. Deleting a CallHippo user permanently removes them from the account, releases their seat and unassigns their numbers. It cannot be undone, it changes what the account is billed, and it severs the link between a body of historical call activity and the person who generated it. That last part is the one people underestimate: the calls stay in the log, but the seat that explains them is gone, and six months later a dispute about what was said to a customer becomes much harder to answer. So the offboarding agent does everything that is safely reversible on its own, closing the call session, archiving the history, unassigning the person from teams, and then stops with a concrete question: "Marcus Webb left on 31 July. His CallHippo seat holds two direct numbers and 340 calls in the last 90 days. Delete the seat and free the licence, or keep it dormant until the retention window closes on 31 October?" The operations owner answers. The billing decision and the records decision are made by the person who is accountable for both, and the agent handles everything either side of it.

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

21 actions

Users and Teams

List Users Retrieves every user on the CallHippo account with their identifier, name and email. It takes no pagination parameters, so it is the cheapest way to resolve an agent's ID before assigning a call, a contact or a campaign.
Get User Retrieves the full profile of one user by ID, including the numbers and teams assigned to them. Used to confirm an agent is provisioned before routing work to them, and to see what a deletion would release.
Delete User Permanently removes a user from the account, releasing their seat and unassigning their numbers. This cannot be undone and affects billing, which is why it belongs behind an explicit approval rather than inside an unattended offboarding job.
Update User Status Sets the availability status of a user, identified by their email address rather than their ID. Used to flip agents online at the start of a shift or take them off the queue when another system marks them busy.
Update User Call Session Starts or stops a user's calling session, which controls whether CallHippo routes calls to that agent at all. Used to open sessions on a schedule and close them at the end of a shift so calls stop ringing an unattended device.
List Teams Retrieves the teams configured on the account, one page at a time. Teams group agents for shared number routing, so this is how a flow discovers which team owns a number before reassigning work.

Contacts

List Contacts Retrieves the contacts belonging to one user, one page at a time, with an optional cut-off so only records changed since a given day are returned. CallHippo caps the page size at 500.
Create Contact Adds a contact to the address book so inbound calls from that number resolve to a name and outbound dialling can be triggered by contact. Numbers should be supplied in international format including the country code.
Update Contact Updates an existing contact. Only the fields supplied are sent, so a flow can correct just the number or just the email without clearing the rest of the record.
Delete Contact Permanently removes a contact from the address book. Calls from that number show as unknown afterwards and the record cannot be recovered.

Calls and Messages

Make Call Places a real, billable outbound call. CallHippo rings the agent's device first, then connects the destination number, so the from number must be one that agent is allowed to use.
List Call Logs Retrieves the call activity feed for a date range: every inbound and outbound call with its duration, outcome and recording. It can be narrowed to a single call by SID or to the CRM record a call was linked to. Because CallHippo publishes no webhooks, this is the endpoint flows poll.
List SMS Logs Retrieves the SMS history for a date range, optionally narrowed to one message ID or a specific sender or recipient number. Like the call feed, this is polled rather than pushed.
Delete Call Reminder Removes a scheduled call reminder so the agent is no longer prompted to call back. Used when the follow-up was already handled through another channel and the reminder would duplicate it.

Do Not Call

Add Do Not Call Number Adds a number to the account's do not call list so CallHippo blocks it, in one or both directions. Used to honour an opt-out the moment it arrives in another system and keep outbound campaigns compliant.
Remove Do Not Call Number Removes a number from the do not call list, restoring calling in both directions regardless of how it was originally blocked. Used when a contact opts back in.

Dialler Campaigns

List Campaigns Retrieves outbound dialler campaigns with their name, description, owner, completed and failed call counts, machine detection setting and creation date. Filter by dialler type to separate power, predictive and speed to dial campaigns.
Get Campaign Retrieves one campaign by ID with its configuration and progress counters. Used to check whether a campaign has finished before starting the next one.
Delete Campaign Permanently removes a dialler campaign and its queued contact list. Calls already placed stay in the activity feed, but the campaign and its pending queue cannot be recovered.
Control Campaign Starts or stops a dialler campaign, which begins or pauses real, billable outbound calling to its whole contact queue. Used to hold campaigns inside approved calling hours, or to stop one immediately when a compliance check fails.
List Campaign Contacts Retrieves the contact queue of a campaign with each lead's name, number, lead ID, attempt count and the action taken. Pages with a page number and size and reports whether more records remain through a hasNext flag rather than a total count.

Frequently Asked Questions

What can FlowRunner do with CallHippo?

FlowRunner agents can run List Users, Get User, and Delete User in CallHippo, plus 18 more actions.

Does connecting CallHippo to FlowRunner require OAuth?

No. CallHippo connects to FlowRunner with an API key, no OAuth flow required.

Can CallHippo trigger a FlowRunner workflow automatically?

CallHippo doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with CallHippo

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us