KrispCall
Voice & TelephonyWork with virtual numbers, calls, SMS, and contacts on KrispCall. Agents provision numbers per campaign or region and log every conversation against the right record.
What This Integration Enables
KrispCall gives a team virtual numbers that customers can call back, and that single fact shapes everything else about it. A workspace number is not a send-only channel. It carries voice, SMS, MMS, and voicemail abilities that vary number by number, it belongs to a specific agent, it can be shared, and the workspace itself carries a KYC verification state that determines whether messaging is permitted in some regions at all. Sending from KrispCall means participating in a two-way relationship with a real person who can reply, complain, or block you.
The connector reflects that. Alongside the obvious surface of numbers, calls, messages, and contacts sits a set of restriction actions that most outreach tooling does not bother to expose: List Do Not Disturb Contacts returns the people a workspace member has muted, and List Blocked Contacts returns the numbers that cannot reach you and that you should not be reaching. FlowRunner agents treat those as the first step of any outreach flow rather than a post-mortem query. That is the practical shape of automation exceptions in a messaging context: most of the list is safe to send and the agent handles it without asking, while the small remainder that hits a mute, a block, or a number without the right ability becomes a short queue for a person to rule on.
There is no KrispCall trigger on this connector, and the page will not pretend otherwise. Flows here start from a schedule or from the system that owns the customer record, and Create Webhook exists as an action for teams that want KrispCall events delivered to their own endpoint. Note that KrispCall publishes no endpoint for deleting a webhook, so a subscription created through this action stays on the account until KrispCall support removes it. Create them deliberately, once, rather than on every flow run.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Call Summarized onto the Account
A rep finishes a discovery call on a workspace number. On its next pass the agent reads List Calls for that customer number, pulls the full record with Get Call, and takes the recording URL and transcript it returns. It summarizes the conversation, extracts the commitments made, and writes both onto the account in HubSpot as a note attached to the deal. The rep does not write a call log. The account has one anyway, and it quotes what was actually said rather than what was remembered an hour later.
Address Book Kept Honest in Both Directions
Contacts drift. A number changes in the CRM and KrispCall keeps showing the old one, so inbound calls arrive as unknown and nobody picks up. An agent runs a two-way sync: List Contacts against the CRM's records, Create Contact for people who exist in the CRM but not in the workspace, and Update Contact where the primary number, company, or tags have moved. Because KrispCall contacts carry secondary numbers and email addresses, the sync keeps a customer's mobile and desk line on the same record instead of creating a second one. The payoff is small and constant: inbound calls resolve to a name, so the person answering knows who is calling before they say hello.
Delivery Confirmed Before Escalating to a Call
A time-sensitive notice goes out by SMS. Rather than assuming it landed, the agent reads Get SMS a few minutes later and branches on the delivery status. Messages confirmed delivered are done. Messages that failed or stalled move to a callback queue, where the agent resolves the owning rep from Get Member and hands them the account with the failed message attached. The escalation from text to voice happens because a delivery status said so, not because someone noticed a week later that a customer never replied.
Human-in-Loop Highlight
Send SMS places a real, billable message on the network, and once it leaves there is no recall. The gate that matters on this connector, though, is not the wording of the message. It is the list.
KrispCall knows things about your recipients that the CRM does not. A workspace member has muted a contact under Do Not Disturb because that customer asked to be left alone. A number sits on the blocked list because someone escalated. A sending number turns out to be voice-only and cannot deliver a message at all. So a FlowRunner outreach agent screens the batch against List Blocked Contacts and List Do Not Disturb Contacts before composing anything, verifies the sending number's abilities with List Numbers, and then stops with the residue: "412 of 431 renewal reminders are clear to send from +1 415 555 0142. 14 recipients are on Do Not Disturb, muted by Priya and Marcus. 5 are blocked. Send the 412 and leave the rest, or do you want the muted ones reviewed first?"
The agent has taken the decision the campaign owner would have made on 412 records and made it. It has not taken the nineteen decisions that involve a customer who already said something about being contacted. That is human-in-the-loop drawn where the cost is real, because a message to someone who opted out is billable, unrecallable, and the kind of thing a customer remembers.
Agent Capabilities
22 actionsWorkspace
3- Get Workspace Retrieves the connected workspace with its title, status, organization identifier, owner details, and KYC verification state. Worth calling as a guard before any write operation, since an unverified workspace cannot send messages in some regions.
- List Members Retrieves the workspace members with their email address, name, and the workspace they belong to. Used to map a KrispCall agent identifier from a call or message onto a real person before notifying them.
- Get Member Retrieves one member by UUID with their full profile and workspace record. Used after a call event carries an agent identifier and the flow needs to reach that person.
Numbers
2- List Numbers Retrieves the workspace's virtual numbers with their short ID, friendly name, type, country, extension, status, owning agent, sharing flag, and the abilities each number has for SMS, MMS, voice, and voicemail. The abilities are the important part, because a voice-only number cannot deliver a message.
- Get Number Retrieves one number by its dialable digits with its type, status, extension, owning agent, sharing flag, and messaging and calling abilities. Supply the country code when the same digits exist in more than one country.
Calls
2- List Calls Retrieves the call history between one external number and one of your KrispCall numbers. Both numbers are required, so this reads a single conversation rather than a whole workspace log. Each record carries direction, status, duration, rating, agent, notes, recording URL, and any transcript.
- Get Call Retrieves one call by identifier with the full record, including the recording URL and transcript. This is the action that feeds a conversation into a summarization or quality step.
Messaging
4- List SMS Retrieves the message history between one external number and one of your numbers, reading a single thread. Each record carries direction, delivery status, conversation status, rating, agent, and the message body.
- Get SMS Retrieves one message by identifier with its body, delivery status, conversation status, direction, agent, and timestamps. Used to confirm a message reached the handset before escalating to a call.
- List Number Messages Retrieves every message sent to or from one KrispCall number across all contacts, rather than a single thread. Unlike List SMS this endpoint filters server side, so the direction and conversation status chosen are applied by KrispCall.
- Send SMS Sends a real, billable text or MMS message from one of your numbers. The sending number is identified by its short ID from List Numbers, not by its digits, and it must have the SMS or MMS ability enabled. Every call places a chargeable message on the network, so this belongs behind explicit conditions.
Contacts
5- List Contacts Retrieves the workspace address book with each contact's number, name, email, company, address, tags, visibility, favourite flag, blocked flag, and read state. Used to sync contacts into a CRM or to check whether an inbound caller is already known.
- Get Contact Retrieves one contact by identifier, adding the creating user, the client identifier, and any secondary phone numbers and email addresses held against the record.
- Create Contact Adds a contact to the address book so calls and messages from that number resolve to a name instead of showing as unknown. Only the phone number is required.
- Update Contact Replaces the details held against an existing contact, including the primary number, name, email, company, address, tags, and secondary numbers and emails. Used to keep the address book in step with a CRM.
- Delete Contact Permanently removes a contact from the address book. Call and message history is retained, but the number stops resolving to a name. This cannot be undone.
Restrictions
4- List Do Not Disturb Contacts Retrieves the contacts placed on Do Not Disturb by workspace members. KrispCall suppresses notifications for these contacts, which makes this the screen to run before an outreach flow dials or messages anyone.
- Get Do Not Disturb Contact Retrieves one Do Not Disturb record, showing which contact is muted and which member muted them. Used to explain to an operator why a contact was skipped.
- List Blocked Contacts Retrieves the contacts blocked in the workspace. Blocked numbers cannot reach your numbers, so screening an outbound list against this avoids spending on records that cannot answer.
- Get Blocked Contact Retrieves one block record with the blocked number and the member who blocked it. Used to audit a block before an operator asks for it to be lifted.
Webhooks
2- Create Webhook Registers a webhook that posts call, SMS, or contact events to your endpoint, optionally with an authentication scheme applied to each delivery. KrispCall publishes no endpoint for deleting a webhook, so a subscription created here stays on the account until KrispCall support removes it. Create these once, deliberately, rather than on every flow run. The vendor flags this feature as Beta.
- Get Webhook Retrieves one webhook subscription with the watched entity, subscribed event types, destination URL, and current status. Used to confirm a subscription is still live, since KrispCall provides no way to list or delete subscriptions through the API.
Frequently Asked Questions
What can FlowRunner do with KrispCall?
FlowRunner agents can run Get Workspace, List Members, and Get Member in KrispCall, plus 19 more actions.
Does connecting KrispCall to FlowRunner require OAuth?
No. KrispCall connects to FlowRunner with an API key, no OAuth flow required.
Can KrispCall trigger a FlowRunner workflow automatically?
KrispCall doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with KrispCall
$100 in credits. No card required. Connect in minutes.