Skip to main content
The First Step
Oct 29, 2026 4:46 PM UTC
Question

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!

    4 replies

    PM AutoThe First StepAuthor
    The First Step
    Oct 30, 2026 7:40 PM UTC

    Hello,

    I have an important update regarding the excessive Pipedrive API usage caused by RingCentral App Connect.

    Our case was escalated to Pipedrive's engineering team, and they have now identified the exact source and behavior of the excessive requests.

    Pipedrive's engineering findings:

    • App name: RingCentral App Connect

    • OAuth client ID: 5d4736e322561f57

    • Pipedrive user ID: 24862441

    • User agent: axios/1.18.1

    • Endpoint: GET /api/v2/persons/search

    • Approximately 250–500 contact searches per hour, continuously, including overnight

    • The app does not slow down after receiving HTTP 429 responses

    • Requests continue even after the daily API allowance is exhausted

    • Approximately 350 rejected requests per hour were observed between 20:00 and midnight UTC

    • An additional 45 POST /api/v2/activities requests failed with HTTP 400

    Pipedrive's engineers believe implementing proper backoff after HTTP 429 responses and caching contact lookups should resolve the excessive usage.

    Our normal daily API allowance is 120,000 tokens, and these repeated requests are exhausting our allowance and interfering with other important business automations.

    Pipedrive temporarily increased our allowance to 500,000 tokens, but that extension has now expired, and they cannot provide another.

    Could your development team please investigate and prioritize this issue?

    We would also appreciate guidance on whether there is a temporary setting we can disable to stop the repeated contact searches without completely disconnecting RingCentral from Pipedrive.

    We need a solution that allows us to continue using our business phone system and CRM reliably.

    Please let us know if you need additional logs or diagnostic information. We can provide the findings from Pipedrive's engineering team.

    Thank you!

    dakong
    Community Manager
    Community Manager
    Nov 3, 2026 2:47 AM UTC

    ​@PM Auto The most interesting part is:

    • Approximately 250–500 contact searches per hour, continuously, including overnight

    Have you enabled any automatic service? Like AI agents that might call our MCP service?

     

    There’s no obvious change on our side that would cause this problem. And there has been no similar report received from other users.

    PM AutoThe First StepAuthor
    The First Step
    Nov 3, 2026 5:26 PM UTC

    Hi, thanks for looking into this.

    We do use Zapier for various Pipedrive automations, and we occasionally use ChatGPT to access RingCentral and Pipedrive data. However, to my knowledge, we haven't configured any AI agents or automated services to continuously access RingCentral App Connect's MCP server.

    One important finding I'd like to share:

    Since disabling RingCentral App Connect, our Pipedrive API usage has dropped significantly, even though our other Zapier and Pipedrive automations have continued running normally.

    This strongly suggests that the excessive API usage is specifically associated with App Connect or something operating through it, rather than our other automations.

    Given this finding, could your engineering team help us determine:

    1. Whether App Connect performs continuous background contact synchronization or polling that could explain 250–500 searches per hour, even overnight.

    2. Whether an external AI agent or MCP client could have been initiating these requests, and how we could verify that.

    3. Whether there might be a synchronization loop or retry issue, particularly since Pipedrive reported that requests continued even after receiving HTTP 429 rate-limit responses.

    We're happy to provide additional details or logs to help narrow this down.

    We'd really like to identify the root cause so we can safely re-enable App Connect without exhausting our Pipedrive API allowance again.

    Thank you for your help!

    dakong
    Community Manager
    Community Manager
    Nov 4, 2026 5:15 AM UTC

    ​@PM Auto I’m the lead dev and can give you direct answers.

     

    App Connect backend only has endpoints/services that react to client requests. Meaning, if no App Connect client requests sent during say midnight, the server won’t make any API call to Pipedrive.

     

    As for MCP, if it’s not configured, it won’t be triggered.

     

    A good way to check it is taking a look at your account traffic. For that to happen, I’ll need your RingCentral Account ID. If you don’t know it, please ask your RC rep. Once you get it, please send it to da.kong@ringcentral.com