FlowRunner
PricingContact
Theme
Start Free

Ringover

Communication

Connect AI agents to your Ringover phone system. Agents trigger click-to-call, send SMS, read call logs, voicemails, and conversations, and manage contacts, numbers, and users.

16 actions API key available
Ringover website ↗ Platform Documentation ↗ Capability data verified 2026-07-27
The morning callback sweep starts on a schedule
List Voicemails pulls overnight voicemails with caller numbers and recording links
List Contacts matches each caller against the address book
The flow ranks the callback queue by account value and voicemail recency
The sales lead confirms the queue and claims the priority accounts personally
Click to Call rings each assigned rep first, then dials the customer once they answer
Send SMS follows unanswered callbacks with a text from the team's number
The day's callback outcomes land in the reporting sheet

What This Integration Enables

A phone system holds the most perishable data in the company: the missed call from a hot prospect is worth something for about an hour. FlowRunner connects agents to Ringover so that data gets acted on while it is still warm: voicemails become ranked callback queues, call detail records flow into reporting, and outreach happens through Click to Call and Send SMS from the company's own numbers. Click to Call deserves a note for what it is: an action that starts with a human, ringing the rep's device first and dialing the customer only when a person has picked up. - Trigger outbound calls from workflows, with the rep on the line before the customer's phone rings - Send SMS from SMS-enabled company numbers, with conversations readable by the whole team - Pull call history with date, direction, and type filters for CRM sync and reporting - Turn voicemail queues into assigned, prioritized worklists with audio links attached - Resolve numbers, users, groups, and tags to wire routing and attribution correctly

Without FlowRunner

Voicemails age in a queue Overnight messages wait until someone remembers to check the box, and callers call competitors
Call data lives only in the phone system Who called, how long, and what happened never reaches the CRM or the Monday report
Texting is a personal-phone habit Follow-up SMS goes from whichever device is handy, invisible to the team and the record

With FlowRunner

Voicemails become a ranked worklist Every overnight message is matched, prioritized, and assigned before the first coffee
Call history is reporting data Call detail records flow to sheets and dashboards on schedule, direction and duration included
SMS runs from company numbers Texts send from SMS-enabled Ringover lines, threaded in conversations the whole team can read

Use Case Scenarios

The missed-call rescue lane

Every hour, List Calls pulls the latest inbound records and filters missed calls. The flow matches numbers against List Contacts and the CRM in [HubSpot](/integrations/hubspot), ranks by deal stage, and posts the queue to [Slack](/integrations/slack). When a rep claims one, Click to Call rings their device and connects the callback. Calls missed from unknown numbers get a Create Contact stub first, so the second interaction starts with a record instead of a mystery.

Appointment reminders that come from the right number

The evening before, the flow reads tomorrow's bookings from [Google Calendar](/integrations/google-calendar), resolves the sending line with List Numbers, and sends each customer a reminder through Send SMS in E.164 format from the team's SMS-enabled number. Replies land in conversations the team can read with List Conversations, so the "running 10 minutes late" answer reaches the person at the counter, not a rep's personal phone.

Call reporting that survives the phone system

Nightly, List Calls pages through the day's records, joins agents from List Users and tags from List Tags, and appends rows to [Google Sheets](/integrations/google-sheets): direction, duration, group, outcome. Voicemail counts from List Voicemails ride along. The sales manager's Monday view is built from call detail records, not from memory, and the same feed powers the quarterly staffing argument with actual inbound volume by hour.

Human-in-Loop Highlight

Send SMS delivers to a customer's personal phone from the company's number, and a delivered text has no undo. The tempting automation is the drafted reply: an agent reads an inbound thread from List Conversations, writes the answer, and sends it. FlowRunner draws the line one step earlier. The agent assembles the thread, drafts the reply, and holds it with the context attached: this number belongs to a contact with an open deal, the last message asked about pricing, here is the draft. A rep approves, edits, or takes over the thread entirely, and only then does Send SMS fire. The same gate covers the batch case: a reminder run to 200 customers posts its list and template for sign-off before the first message leaves. Drafting and threading are machine work. What arrives on a customer's phone under your number is a human decision.

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

16 actions

Calls

3
  • List Calls Retrieves call history with a filter body covering date range, direction, call type, and pagination, returning up to 1000 calls per request with a total match count. The read behind reporting, CRM sync, and missed-call sweeps.
  • Get Call Retrieves the full detail of a single call by ID: direction, participants, duration, recording availability, notes, and tags. The context pull before a callback decision.
  • Click to Call Initiates a callback that rings the agent's device on the From Number first, then dials the destination once answered. The From Number must be assigned to the calling user. Outbound calling that starts with a human on the line.

Messaging

2
  • Send SMS Sends an SMS from an SMS-enabled Ringover number to a destination in E.164 format, returning the message with ID and delivery status. The customer-reaching write this page's human gate protects.
  • List Conversations Lists SMS conversations with pagination, each grouping the messages exchanged with an external number. The thread-context read before any reply is drafted.

Contacts

5
  • List Contacts Lists address book contacts with pagination and free-text search across names and numbers. The matching step that turns a caller ID into a known relationship.
  • Get Contact Retrieves a single contact by ID with all phone numbers, emails, company, and metadata.
  • Create Contact Creates an address book contact with at least a name and one E.164 phone number, returning the assigned contact ID. Used to give unknown callers a record before the second interaction.
  • Update Contact Updates a contact by ID, changing only supplied fields. Note that supplied phone number or email lists replace the existing ones.
  • Delete Contact Permanently deletes a contact from the address book. This cannot be undone, so cleanup flows route deletions through review.

Account and Routing

6
  • List Numbers Lists the provisioned phone numbers with country, format, group, and status. The lookup for choosing a From Number for calls and SMS.
  • List Users Lists the account's users with name, email, extension, assigned numbers, and presence. Used for attribution and callback assignment.
  • Get User Retrieves a single user by ID with profile, extension, numbers, and current availability. The check before routing a callback to someone who is actually online.
  • List Groups Lists the call groups with members and associated numbers. The routing map for inbound distribution.
  • List Tags Lists the account's tags with ID, name, and color. Used to categorize calls and conversations consistently in reporting.
  • List Voicemails Lists voicemails with pagination and date filtering, each carrying the caller's number, duration, timestamp, and an audio link where available. The source feed for the morning callback queue.

Frequently Asked Questions

What can FlowRunner do with Ringover?

FlowRunner agents can run List Calls, Get Call, and Click to Call in Ringover, plus 13 more actions.

Does connecting Ringover to FlowRunner require OAuth?

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

Can Ringover trigger a FlowRunner workflow automatically?

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

Start building with Ringover

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