Calley

Feed and monitor Calley auto-dialer campaigns, pushing contacts into calling lists individually or in bulk. Agents build the day's call list from live pipeline data and read call outcomes back.

1 trigger 6 actions API key available

Calley website ↗ Platform Documentation ↗ Capability data verified 2026-08-03

Agent reads the accounts that went quiet, the trials that expired and the renewals due, from the systems that hold them

Agent calls Get Agents to resolve the reps on the TEAMS account and Get Calling Lists to find the right list

Agent removes anyone already contacted this week by reading Get List Call Data on the current list

Agent posts tomorrow's proposed list with the per-rep split and the reason each contact made the cut

The sales manager confirms or reshuffles the assignment

Agent pushes the confirmed list with Add or Update Multiple Contacts, each contact tagged to its agent by ID

What This Integration Enables

Calley is the one connector in this category where no AI does the talking. Calley is an auto-dialer that runs on a rep's phone: it takes a calling list, dials the next number, and hands a live human being a conversation. The status, notes and feedback that come back are written by the person who made the call. That makes Calley a different proposition from a voice agent platform, and a more literal expression of the same argument FlowRunner makes everywhere else. The machine prepares the work. The person does the part that needs a person.

The connector's surface is small on purpose. Agents read the account's calling lists and the reps attached to them, push contacts into a list one at a time or in bulk with per-agent assignment on TEAMS accounts, pull back the full call data for a list including each contact's status, rescheduled state, agent name, notes and feedback, and page through call detail records for a date range. What that buys is a calling list assembled from live data instead of a stale export, and outcomes that land back in the CRM instead of dying in the dialer. It is worth noting what the connector does not have: there is no action to remove a contact from a list. Contacts go in, and taking one out again is a manual job in the Calley panel.

Without FlowRunner

The list is built by hand Someone spends the last hour of the day pulling names into a spreadsheet

Assignment is informal Who calls whom is decided in the morning huddle, or not at all

Outcomes stay in the dialer Rep notes and call statuses sit in Calley and never reach the CRM

With FlowRunner

The list builds itself Contacts arrive from the systems that already know who is worth calling

Assignment is explicit Every contact carries an agent ID, and the manager approved the split

Outcomes come back Statuses, notes and feedback flow from the calling list into the record that needed them

Use Case Scenarios

Tomorrow's call list, built from today's signals

At the end of the day a flow reads the accounts that stopped logging in, the trials that expire this week and the renewals coming due. The agent scores them, resolves the rep roster with Get Agents, and checks Get List Call Data on the current list so nobody gets called twice in a week. It proposes a split: the renewals to the account manager who owns them, the expired trials to the SDR who ran the outreach. The manager adjusts two assignments and confirms. The agent pushes the whole thing with Add or Update Multiple Contacts, each contact carrying its name, notes and agent ID. The reps open Calley in the morning to a list that already knows why each name is on it.

One lead, one contact, straight into the queue

A high-intent form submission arrives. Rather than waiting for the nightly build, the agent calls Add or Update Contact to drop that single contact into the live calling list with the notes field carrying what the person asked for. The rep working the list reaches them the same afternoon, with context, rather than reading a name and a number.

Rep notes flowing back into the record

The On New Call Detail trigger fires as call detail records appear. The agent reads the outcome, the rescheduled status, and the notes and feedback the rep typed after the conversation, then writes them onto the matching record in HubSpot and posts the ones marked for follow-up into Slack. A rep who wrote "wants to talk after the board meeting on the 14th" has that turn into a task, not a note in an app the rest of the company never opens.

Human-in-Loop Highlight

The gate is Add or Update Multiple Contacts, and what makes it consequential is not the writing, it is the assignment. Each contact in a bulk push carries an agent ID, and that field decides whose day tomorrow is. Push 300 renewal accounts to the wrong rep and a person spends eight hours having conversations they are not equipped to have, with customers who will remember it. The push is also difficult to walk back, because this connector has no action that removes a contact from a list; correcting a bad bulk load means someone editing lists by hand in the Calley panel while the reps are already dialling. So the agent builds the list, resolves the reps with Get Agents, and stops: "Tomorrow's list is 214 contacts. 96 renewals to Dana, 78 expired trials to Marcus, 40 quiet accounts unassigned because they have no owner. Confirm, or reassign before I push." The manager answers, the agent pushes exactly what was approved, and the reps get a day that somebody chose. That is human-in-the-loop on the decision that shapes other people's work, which is the kind worth stopping for.

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

6 actions

Calling Lists

Get Calling Lists Retrieves all calling lists created by the account, each with its unique identifier, list ID and list name. Used to resolve the target list by name before any contact is written to it.
Get List Call Data Retrieves the full calling details of a list: call ID, contact name, mobile number, call status, rescheduled status, agent name, notes and feedback for every contact in the list. This is where the rep's own words come back into the flow.

Agents

Get Agents Retrieves all agents connected to the team admin account, each with agent ID, name and email address. Available on Calley TEAMS accounts, and the lookup that makes per-rep assignment possible.

Contacts

Add or Update Contact Adds a contact to a calling list or updates an existing one, taking the mobile number, calling list ID, name and notes. A TEAMS admin can also assign the contact to a specific agent by agent ID. Returns the stored contact with its name, call status, notes, mobile number and list ID.
Add or Update Multiple Contacts Adds or updates multiple contacts in one request on a TEAMS account, each carrying its own mobile number, calling list ID, name, notes and agent assignment. Used to load a full day of calling in a single write.

Call Details

Get Call Details Retrieves detailed call data for a date range, one page at a time, taking the from date, to date and page number. Used to sync outcomes into a reporting sheet or warehouse on a schedule.

Triggers

1 triggers

Event Triggers

On New Call Detail Fires when a new call detail record appears on the account. Used to start follow-up the moment a rep finishes a conversation: write the outcome and the rep's notes back to the CRM, create the task they asked for, or route a flagged call to a manager.

Frequently Asked Questions

What can FlowRunner do with Calley?

FlowRunner agents can run Get Calling Lists, Get List Call Data, and Get Agents in Calley, plus 3 more actions.

Does connecting Calley to FlowRunner require OAuth?

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

Can Calley trigger a FlowRunner workflow automatically?

Yes. Calley supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Calley

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

Start Building Free Talk to us