Already have an account? Sign in

RingCentral (v1)

RingCentral feature snapshot

A high-level look at Stitch's RingCentral (v1) integration, including release status, useful links, and the features supported in Stitch.

Connecting RingCentral

Step 1: Generate RingCentral credentials

• Step 1.1: Create a RingCentral developer application

• Step 1.2: Retrieve application credentials

Step 1.1: Create a RingCentral developer application

In this step, you’ll create a RingCentral developer application.

1. Navigate to theRingCentral Developer Console.
2. Create a free account, if you don’t already have one.
3. After you’ve created an account and logged in, click theCreate App button.

4. In the window that displays, enter a name and description for the app.
5. In theApp Type & Platform window, fill in the fields as follows:
   • Application Type: SelectPrivate.
   • Platform Type: SelectServer-only (No UI).
6. ClickNext.

7. Next, you’ll grant permissions to the app. In thePermissions Needed field, select the following:
   • Read Accounts
   • Read Call Log
   • Read Messages
8. ClickCreate.

Step 1.2: Retrieve application credentials

After your application is created, you’ll retrieve its credentials.

1. On theApps page, click the developer application you created in the previous step.
2. Click theCredentials option in the menu on the left side of the page.

3. In theApplication Credentials section, locate the following in theProduction Environment column:

   • API Server URL
   • Client ID
   • Client Secret

Keep this page handy for now - you’ll need it to complete the setup in Stitch.

Step 2: Add RingCentral as a Stitch data source

1. Sign into your Stitch account.

2. On the Stitch Dashboard page, click theAdd Integration button.

3. Click theRingCentral icon.

4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

   For example, the name “Stitch RingCentral” would create a schema calledstitch_ringcentral in the destination.Note: Schema names cannot be changed after you save the integration.

5. In theClient ID field, enter theClient ID fromStep 1.2.
6. In theClient Secret field, enter theClient Secret fromStep 1.2.
7. In theUsername field, enter the username for the RingCentral developer app. This is typically the phone number used to create the app.
8. In thePassword field, enter the password for the RingCentral developer app.
9. In theAPI URL field, enter theAPI Server URL fromStep 1.2.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your RingCentral integration. This means that dataequal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond RingCentral’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In theReplication Frequency section, you’ll create the integration’sreplication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

RingCentral integrations support the following replication scheduling methods:

• Replication Frequency

• Anchor Scheduling

• Advanced Scheduling using Cron (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 5: Set objects to replicate

The last step is to select the tables and columns you want to replicate.Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

• Selection options
• Individual tables and columns
• All tables and columns

Initial and historical replication jobs

After you finish setting up RingCentral, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

RingCentral table reference

Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.