Onoff Business

Manage members, numbers, departments, contacts, and call and SMS logs on Onoff Business. Agents provision business lines and keep call activity attached to the right record.

21 actions API key available

Onoff Business website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

The HR system records an employee's last working day

Agent resolves the member with Get Member and reads the numbers and departments attached to them

Agent looks at inbound volume on that number over the last quarter with List Calls

Agent identifies the customers who have called it most and the department that would inherit the line

Agent posts the number, its call history, and the proposed successor to the people ops channel

The manager chooses reassign or release, and the agent runs Assign Number or Release Number accordingly

What This Integration Enables

Onoff Business is not really a phone system. It is a record of who in your company has which business line, and it is at its most useful in the two weeks around somebody joining or leaving. The connector's surface says as much: members, numbers, departments, contacts, and the logs that tie them together. There is no dialer, no IVR builder, no queue. What there is instead is the mapping between people and lines, which is exactly the thing that goes stale when nobody owns it.

That makes this one of the connectors that belongs in a joiner and leaver flow rather than a sales flow. On the way in, an agent creates the member, places them in the right departments, finds a free line with List Numbers, and assigns it, so a new hire has a working business number before their first call. On the way out, the same flow runs in reverse and hits a question that no HR system can answer on its own: what happens to the number. One structural detail shapes a lot of this. Contacts in Onoff Business belong to individual members rather than to the organisation, so a departing person's address book is theirs, and reading it into the CRM before the account is closed is not an optional nicety. It is the only chance.

Without FlowRunner

Lines outlive their owners A departed employee's number keeps ringing an account nobody monitors

Offboarding forgets the phone Systems access is revoked on the last day and the business line is dealt with weeks later

Customer history walks out The address book lived on one person's account and left with them

With FlowRunner

Telephony inside the leaver process The number is handled on the same day as everything else, by the same flow

The line's value is visible Whoever decides can see how many customers actually call it before it goes

Contacts recovered first A member's address book is read and preserved before the account is closed out

Use Case Scenarios

A New Hire Has a Line on Day One

A record appears in BambooHR with a start date. On the morning of that date an agent calls Create Member with the person's name, work email, and the departments matching their role, which sends the Onoff Business invitation to an address they can actually receive. It then calls List Numbers filtered to available inventory, picks a line in the right country, and assigns it with Assign Number. The new hire's first day includes a phone number that already routes to them and already sits in the right department for reporting. Nobody filed a ticket.

Address Book Synced Per Member

Because contacts belong to members, an organisation-wide sync has to walk the roster. An agent reads List Members, then for each person runs List Contacts against their book, pages through the opaque cursor, and reconciles the entries against the CRM. Names on the CRM that the member does not have get pushed with Create Contact so their inbound calls resolve instead of showing a raw number, and numbers the member holds that the CRM has never seen are surfaced as a short list for the account owner to review. The result is that a customer calling any line in the company reaches someone whose handset knows who they are.

Weekly Call Volumes Where the Team Already Looks

Every Monday an agent calls Get Statistics for the previous week with the office timezone supplied so day boundaries line up with working hours. The response carries inbound and outbound counts, answered, missed, and offline-missed outcomes, total talk time, messages sent and received, voicemails, and a breakdown of calls by duration band. The agent turns that into a short read and posts it to Slack, calling out the numbers where missed calls moved rather than dumping the whole table. When a specific line is behind, the agent pulls that member's List Calls for the week so the follow-up conversation starts with the actual calls.

Human-in-Loop Highlight

Release Number is the one action on this connector that a leaver flow must not take on its own. It removes a virtual number from the organisation, and Onoff Business is explicit that the number may be returned to the carrier pool rather than held for later reuse. That is not a revocation. It is a disposal. A support line that customers have dialled for three years, printed on invoices and saved in their phones, can be gone at the end of a routine offboarding run, and no amount of apologising gets it back.

So a FlowRunner offboarding agent completes every reversible part of the leaver process, then stops with a question it has already done the research for. It reads the departing member's numbers from Get Member, pulls the last quarter of List Calls on each line, and puts the actual pattern in front of the manager: "Marcus leaves Friday. His line +33 1 xx xx 41 12 took 96 inbound calls last quarter from 31 distinct customers, 12 of them in the last two weeks. His second line took 3. Reassign the first to Amélie and release the second, or hold both?" The manager answers, and the agent runs Assign Number for one and Release Number for the other.

This is human-in-the-loop doing the thing it is actually for. The agent is not asking because it lacks permission. It is asking because the decision turns on what the business wants the number to mean, and that is not derivable from the HR record that started the flow.

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

Members

List Members Retrieves the people in the organisation with their name, email, and the departments and numbers assigned to them. Results page with an opaque forward cursor, so a flow passes the previous nextOffset and stops when it comes back empty.
Get Member Retrieves a single member with their name, email, and linked departments and numbers. This is the read that tells an offboarding flow exactly which lines are about to become unowned.
Create Member Adds a person to the organisation and optionally places them in departments. The invitation is sent to the email address supplied, so it must be one they can receive mail at. New members default to the standard user role unless an administrator role is chosen.

Numbers

List Numbers Retrieves the organisation's virtual numbers filtered by whether they are free or already assigned, with the member holding each one and its expiry date. A status is required, so a provisioning flow asks for available numbers and an audit flow asks for in-use ones.
Get Number Retrieves one number with its creation date, current holder, country, whether it is a landline, and when the subscription expires. Used to check an expiry before renewal or to confirm ownership before changing anything.
Assign Number Hands an available number to a member so calls and messages on it route to them. The number is identified by its dialable digits rather than an internal identifier, and assigning one already in use is rejected, so a flow checks availability first.
Release Number Removes a virtual number from the organisation. The number stops receiving calls and messages and may be returned to the carrier pool rather than held for reuse. This is the action to put behind a named human decision in every flow that touches it.

Departments

List Departments Retrieves the organisation's departments with their identifier, name, and emoji badge. Used to resolve a department name to the identifier that member operations expect.
Create Department Creates a department that members can be grouped into. Both a name and an emoji badge are required, because the emoji is how the department is identified visually in the console.
Update Department Renames a department or changes its emoji badge. Both values are required, so a flow reads the current department first when only one of them is changing. Membership is unaffected.
Delete Department Permanently removes a department. Members that belonged to it are not deleted but lose the grouping, so any reporting or routing based on it stops applying. This cannot be undone.

Contacts

List Contacts Retrieves the address book of one member, since contacts belong to individual members rather than the organisation. Each contact carries a name, an email, and one or more typed phone numbers, and a search term matches by name.
Get Contact Retrieves one contact from a member's book. The owning member must be supplied alongside the contact identifier, because the identifier is only meaningful within that member's book.
Create Contact Adds a contact to one member's address book so calls and messages show a name instead of a raw number. At least one phone number is required, and each entry pairs a type label with the number in international format.
Delete Contact Permanently removes a contact from one member's book. Logged calls and messages keep their history but stop resolving to a name. This cannot be undone.

Calls and Voicemail

List Calls Retrieves one member's call log over a date window with the external party, the virtual number used, direction, duration, and outcome. A start date, an end date, and a member are all required, so this reads a person's activity rather than the organisation's.
Get Call Recording Returns a pre-signed download URL for a call recording. The URL expires roughly ten minutes after it is issued, so a flow fetches or stores the audio in the same run rather than saving the link for later.
Get Voicemail Returns a pre-signed download URL for a voicemail left on one of the organisation's numbers, with the same ten minute expiry. Pass it straight to a transcription or storage step so a missed call becomes readable text on the record.

Messaging

List Messages Retrieves one member's SMS log over a date window, covering sent and received messages with the body, the external number, the virtual number used, and the conversation thread each belongs to. The returned thread reference feeds List Thread Messages.
List Thread Messages Retrieves every message in one conversation thread for a member, in stored order. Used to reconstruct a full exchange with a customer once List Messages has identified which thread matters.

Statistics

Get Statistics Returns organisation-wide telephony totals for a date window: inbound and outbound call counts, answered, missed, offline-missed and other outcomes, total talk time, messages sent and received, voicemails, and a breakdown of calls by duration band. Supply a timezone so day boundaries line up with the team's working hours rather than UTC.

Frequently Asked Questions

What can FlowRunner do with Onoff Business?

FlowRunner agents can run List Members, Get Member, and Create Member in Onoff Business, plus 18 more actions.

Does connecting Onoff Business to FlowRunner require OAuth?

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

Can Onoff Business trigger a FlowRunner workflow automatically?

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

Start building with Onoff Business

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

Start Building Free Talk to us