Articles in this section

Set up a connection to RingCentral

Naga Sri Hari Gonaboyina
Updated

RingCentral is a cloud communications platform that lets businesses send and receive calls or texts across multiple devices.

Note

If you want to connect to the Contact center API, Celigo recommends using the Nice CXone connector.

Set up a connection

After you start the connection, configure it in the Create connection panel and complete all of the required * authentication settings:

Setting

Instructions

Name your connection * 

Enter a clear and distinguishable name.

Throughout integrator.io imports and exports, you will have the option to choose this new connection. A unique identifier will prove helpful later when selecting it from a list of the connections in your account.

API type * 

Choose your RingCentral API type:

  • MVP: Manage messaging, voice, and phone system features to integrate calling, SMS, fax, and voicemail into your business workflows.

  • Video: Enable video conferencing and meeting management to schedule, start, and control video meetings programmatically.

  • CX: Power customer experience solutions like contact center interactions to manage agent routing, customer journeys, and analytics.

  • Events: Receive real-time notifications about system or user events to trigger workflows or monitor activity through webhooks.

Tip

This connector documentation describes only the settings shown for the Simple view. For the corresponding HTTP settings, see OAuth 2.0 auth universal connector documentation.

API type: MVP and Video

Setting

Instructions

Environment * 

Select your RingCentral account environment type:

  • Production: if your RingCentral account URL is

    https://platform.ringcentral.com 

  • Sandbox: if your RingCentral account URL is

    https://platform.devtest.ringcentral.com 

OAuth 2.0 client * 

Select the OAuth 2.0 client that stores the client ID and client secret provided by RingCentral.

dataLoad.svg​​ How to retrieve the client ID and client secret

To add an OAuth 2.0 client and configure your credentials, click the plus (+) button. Click the edit (pencil.svg) button to modify a selected OAuth 2.0 client. For more information, see Create an OAuth 2.0 iClient resource.

How to retrieve the client ID and client secret

  1. Sign in to your RingCentral developer account.

  2. Navigate to Console > Apps.

  3. Click Create app, select REST API app, and click Next.

  4. Enter an App name and integrator.io Redirect URI.

    • For NA: paste https://integrator.io/connection/oauth2callback

    • For EU: paste https://eu․integrator.io/connection/oauth2callback

  5. Click Create. You will be navigated to the app dashboard.

  6. Copy the Client ID and Client secret.

API type: CX

Setting

Instructions

Product type * 

Select your RingCentral CX product type (either Digital or Voice).

Account name * (This setting is visible only when you select the Digital product type)

Enter your RingCentral account name (subdomain).

Platform hostname * (This setting is visible only when you select the Digital product type)

Enter your RingCentral platform hostname (domain).

Token * 

Enter your RingCentral account token.

Multiple layers of protection, including AES 256 encryption, are in place to keep your token safe. When editing this connection, you must re-enter this value each time; it is stored only when the connection is saved and never displayed as text.

API type: Events

Setting

Insructions

Auth type * 

Choose your RingCentral authentication type (either OAuth 2.0 or Token).

OAuth 2.0 client * 

Select the OAuth 2.0 client that stores the client ID and client secret provided by RingCentral.

dataLoad.svg​​ How to retrieve the client ID and client secret

To add an OAuth 2.0 client and configure your credentials, click the plus (+) button. Click the edit (pencil.svg) button to modify a selected OAuth 2.0 client. For more information, see Create an OAuth 2.0 iClient resource.

Token * 

Enter your RingCentral token.

Multiple layers of protection are in place, including AES 256 encryption, to keep your connection’s token safe. When editing this form later, you must enter this token again; it is stored only when the connection is saved and never displayed as text.

Additional references