RingCentral
Send the right update through RingCentral at the right moment, with a person approving what reaches customers.
37 ways to read, 5 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with RingCentral, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Post to chatApproval by rule
- Create contactApproval by rule
- List active callsRead
Example flow
- RingCentral · List active callsDone
- RingCentral · Post to chatNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches RingCentral.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to RingCentral
- RingCentral's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a RingCentral test account before you go live.
For developers
Technical detail
RingCentral extensions, directory, call log, active calls, messages, presence, contacts, queues, devices, Video meetings and Team Messaging; send one SMS, post to a chat, manage contacts.
RingCentral API docs- Source actions
- 37
- Destination actions
- 5
- Data types
- 26
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Account1
- Get accountSource
Company account details and main number.
Active calls1
- List active callsSource
Calls in progress for the extension, or for the whole account (admin).
Business hours1
- Get business hoursSource
Weekly business hours of an extension, or of the company.
Call log2
- Get call recordSource
One call log record with details.
- List call logSourceIncremental
Calls of the extension, or of the whole account for admins.
Call queue members1
- List call queue membersSource
Extensions that are members of a call queue.
Call queues1
- List call queuesSource
Call queues in the account.
Chat notes1
- List chat notesSourceIncremental
Notes in a chat with title, preview and status.
Chat posts3
- Get chat postSource
One post in a chat.
- List chat postsSource
Posts in a team messaging chat, newest first.
- Post to chatDestinationNot retried automaticallyApproval before production
Posts a message to a team messaging chat.
Chat tasks1
- List chat tasksSourceIncremental
Tasks in a chat with status, assignees and due dates.
Chats2
- Get team messaging chatSource
One chat with its members.
- List team messaging chatsSource
Teams, group chats and direct chats of the user.
Contacts4
- Create contactDestinationNot retried automaticallyApproval before production
Adds a contact to the extension's address book.
- Get contactSource
One address book contact.
- List address book contactsSource
Personal address book contacts of the extension.
- Update contactDestinationProvider duplicate protectionApproval before production
Replaces an address book contact's fields.
Conversations1
- List conversationsSource
Direct, personal and group conversations of the user.
Devices1
- List extension devicesSource
Desk phones, softphones and other devices of an extension.
Directory entries3
- Get directory entrySource
One company directory entry.
- List company directorySource
Company directory entries (users, departments, queues and shared contacts).
- Search company directorySource
Searches the directory by name, extension, phone, email, job title or department. The search text is sent in the request body.
Events2
- Get team messaging eventSource
One Team Messaging calendar event.
- List team messaging eventsSource
Calendar events the user created in Team Messaging.
Extensions2
- Get extensionSource
The extension the connection acts as, or another extension by ID.
- List extensionsSource
Users and other extensions in the account.
Messages3
- Get messageSource
One message-store record.
- List messagesSourceIncremental
SMS, pager, fax and voicemail records in the message store.
- Mark message read or unreadDestinationProvider duplicate protectionApproval before production
Sets the read status of a message.
Persons1
- Get personSource
A Team Messaging user by person ID (for example a post creator).
Phone numbers1
- List extension phone numbersSource
Numbers of the extension with SMS and calling features.
Presence2
- Get presenceSource
Presence, DND and telephony status of the extension or another extension.
- List account presenceSource
Presence, DND and telephony status of every user in the account.
SMS1
- Send SMSDestinationNot retried automaticallyApproval before production
Sends an SMS from an SMS-enabled number of the extension to one recipient.
Tasks1
- Get taskSource
One Team Messaging task.
Teams2
- Get teamSource
One Team Messaging team.
- List teamsSource
Team Messaging teams the user belongs to.
Video bridges1
- Get video bridgeSource
A meeting bridge (personal or scheduled room) and its preferences.
Video meetings2
- Get video meetingSource
One RingCentral Video meeting from history.
- List video meetingsSourceIncremental
RingCentral Video meeting history with participants and AI summaries.
Video recordings1
- List video recordingsSource
RingCentral Video recordings of the authorised user (metadata only).
Access and limits
- 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.
- Pagination
- page/perPage with navigation.nextPage; pageToken/recordCount for Team Messaging.
- Provider events
- Push notification subscriptions (webhooks) for message-store, telephony session and presence events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
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.
- Intentionally excluded: deleting contacts, messages, chats or posts; creating Team Messaging tasks, notes, events or teams; call control (RingOut, transfer, hang-up); creating or ending meetings; bulk SMS. Only a single post to one chat is written in Team Messaging.
- RingCentral Video history, recordings and bridges need the Video scope; recording media links, bridge passwords and dial-in PINs are never mapped.
- The company directory search sends the search text in the POST body, not the URL.
- Account-wide presence, active calls and the company call log need admin permissions.
- SMS, contact and chat post creation have no idempotency key and are not repeated automatically.
Developer reference
- Create the RingCentral credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose RingCentral, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/ringcentral and the Connections API.