RingCentral

Read RingCentral call logs, SMS and messages, extensions, phone numbers, presence, contacts and team chats; send SMS, post to chats and manage contacts.

Log calls and texts against customers, send transactional SMS and keep the company address book in sync.

Build a flow with RingCentral Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

account

Get account
Source
Company account details and main number.

call log

List call log
Source
Incremental
Calls of the extension, or of the whole account for admins.

chat posts

List chat posts
Source
Posts in a team messaging chat, newest first.
Post to chat
Destination
Not retried automatically
Posts a message to a team messaging chat.

chats

List team messaging chats
Source
Teams, group chats and direct chats of the user.

contacts

Create contact
Destination
Not retried automatically
Adds a contact to the extension's address book.
Get contact
Source
One address book contact.
List address book contacts
Source
Personal address book contacts of the extension.
Update contact
Destination
Duplicate protected
Replaces an address book contact's fields.

extensions

Get current extension
Source
The extension the connection acts as.
List extensions
Source
Users and other extensions in the account.

messages

Get message
Source
One message-store record.
List messages
Source
Incremental
SMS, pager, fax and voicemail records in the message store.
Mark message read or unread
Destination
Duplicate protected
Sets the read status of a message.

phone numbers

List extension phone numbers
Source
Numbers of the extension with SMS and calling features.

presence

Get presence
Source
Presence, DND and telephony status of the extension.

sms

Send SMS
Destination
Not retried automatically
Sends an SMS from an SMS-enabled number of the extension to one recipient.

Authentication

RingCentral app (client ID, client secret) with a refresh token

Plans and access

RingEX (MVP) plans with API access; SMS requires a number enabled and registered for SMS (TCR for US A2P). Calls act as the authorised extension; account-wide call logs need admin permissions. SMS senders must be SMS-enabled numbers of the extension.

Test environment

RingCentral developer sandbox accounts are free (sandbox uses platform.devtest.ringcentral.com, not supported here).

Rate limits

Per-user rate groups (Light, Medium, Heavy, Auth) over 60-second windows; HTTP 429 with Retry-After and a penalty interval.

Provider events

Push notification subscriptions (webhooks) for message-store, telephony session and presence events. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

RingCentral refresh tokens expire after about seven days without use; an idle connection must be reauthorised. The JWT bearer grant is not used because the engine cannot send a secret assertion in a token request yet.
SMS goes to exactly one recipient per operation; bulk (A2P batch) SMS is not implemented.
Message store and call log reads default to the last 24 hours unless a start date is supplied.
Contact updates use PUT; fields not sent may be cleared, so map every field you want to keep.
Recordings, voicemail and fax content are not downloaded; deletes and call control are not implemented.
SMS, contact and chat post creation have no idempotency key and are not repeated automatically.