RingCentral App Connect causing excessive Pipedrive API token usage (up to 181K/day)

Hello RingCentral App Connect Team,

We're using RingCentral App Connect with Pipedrive CRM for our automotive repair business, PM Autoworks.

We've recently experienced a massive, unexplained increase in Pipedrive API token usage, and Pipedrive has identified RingCentral App Connect as the source of nearly all of it.

Here's what we're seeing:

• Before October 23, our daily usage was generally between 2,400–8,700 tokens.

• October 23: 48,100 tokens

• October 24: 65,400 tokens

• October 27: 176,900 tokens

• October 28: 181,200 tokens

• October 29: Already 144,202 tokens at the time of this post

According to Pipedrive's API Usage dashboard, RingCentral App Connect consumed 729,178 tokens over the last 7 days, accounting for 98.17% of our total API usage.

Our normal daily Pipedrive limit is 120,000 tokens. Pipedrive Support has temporarily increased this to 500,000 while the issue is investigated.

This level of usage seems excessive for our normal call and SMS activity.

Questions for the App Connect engineering team:

1. Is there a known issue with the Pipedrive integration or recent App Connect 2.0 updates that could explain this sudden increase?

2. Is App Connect repeatedly polling Pipedrive for contacts, deals, activities, or call/SMS records? Could an excessive polling frequency, synchronization loop, or retry issue be causing this?

3. Can you help identify which Pipedrive API endpoints App Connect is calling most frequently and whether those calls originate from the browser extension or server-side processes?

4. Are there any settings we can safely adjust to reduce API usage without losing essential call and SMS logging functionality?

5. Is the Pipedrive connector using optimized API v2 endpoints where available?

We would appreciate help identifying the root cause and finding a permanent solution rather than simply increasing our API allowance.

I've attached a screenshot of our Pipedrive API Usage dashboard showing the spike and application breakdown.

RingCentral Developer Support referred us to this community and offered to forward our post to the App Connect engineers.

Thank you for your assistance!