Skip to main content

RingCentral

Nexla's bi-directional connectors can both send data to and receive data from any data system. This means that once a user has created or gained access to a credential for any data system, building any data flow to ingest data from or send data to a location within that data system requires only a few simple steps.

ringcentral_api.png

1. Credentials​

This section provides information about and step-by-step instructions for creating a new RingCentral credential in Nexla.

  • After selecting the data source/destination type, click AddANewCredential.png in the Authenticate screen. This will open the Add New Credential window.

Configure the Credential​

  1. Enter a name for the credential in the Credential Name field.

  2. Optional: Enter a description for the credential in the Credential Description field.

    Resource Descriptions

    Resource descriptions should provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.


  1. Enter or select the following information in the displayed fields:

    • Authorization URL – RingCentral Authorization URL
    • Private App: Client ID – The client ID of the application making the request. Please check RingCentral API documentation for instructions on creating and application.
    • OAuth Nonce – A pass-through value used by the client to maintain state between the request and callback
    • Response Type – RingCentral Response Type
    • Token URL – URL used to get the token for RingCentral
    • Client ID for Token URL – The client ID of the application making the request. Please check RingCentral API documentation for instructions on creating and application.
    • Private App: Client Secret – The Client Secret of the application making the request. Please check RingCentral API documentation for instructions on creating and application.
    • Token Grant Type – RingCentral grant type for Token URL
    • Authorization Header: Base64(Client ID:Secret) – The RingCentral API requires the Client ID and Secret to be specified as a base64 encoded pair. Enter the resulting string obtained after base64 encoding "<ClientID>:<ClientSecret>".

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save.png button at the bottom of the Add New Credential screen to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.


2. Data Source​

To ingest data from a RingCentral location, follow the instructions in Section 2 of Common Setup for REST API-Based Systems.


3. Data Destination​

To send data to a RingCentral location, follow the instructions in Section 3 of Common Setup for Databases and Data Warehouses.