I’m hoping someone else has run into this because RingCentral support has been completely useless.
We’ve been using RingCentral with Google Workspace for over a year. Our contacts sync between RingCentral and Google Contacts without any issues. Then suddenly, starting this week, everything broke.
The issue
Any time we try to:
-
Create a new contact in RingCentral
-
Edit an existing Google-synced contact
We get this error:
“Sorry, something went wrong on our end and we weren't able to save the contact. Try again later.”
This happens:
-
On desktop app
-
On mobile app
-
On multiple devices
-
On multiple users
So it’s clearly not a device or browser issue.
What we’ve already tested
We’ve done all the usual troubleshooting:
-
Disconnected and reconnected Google integration
-
Reauthorized all permissions
-
Checked Google Admin settings
-
Confirmed RingCentral is a trusted app
-
Verified we can create contacts directly in Google
-
Cleared sessions, re-logged, etc.
Nothing fixed it.
The key test
We connected the same RingCentral account to a personal Gmail account instead of our Google Workspace account.
Result:
-
Works perfectly
-
Contacts save with no errors
So:
-
RingCentral → personal Gmail = works
-
RingCentral → Google Workspace = fails
Even more confusing
We use Zapier to create Google contacts from new calls.
At first, those automations were failing with:
-
412 Precondition Failed error
Now:
-
Zapier contact creation is working again
-
But RingCentral still cannot create or edit contacts
So Google is clearly accepting contact writes again.
That makes me think:
-
Google changed something in their contacts API
-
Zapier updated their integration
-
RingCentral hasn’t
RingCentral’s response
Here’s what Tier 2 support told me:
They said if it works with personal Gmail, then it must be a Google Workspace permission issue and told me to contact Google.
But:
-
Nothing changed in our Workspace
-
It worked for over a year
-
Zapier can now write contacts again
-
Only RingCentral is failing
This really feels like a RingCentral API or scope issue, not a Google admin problem.
Error in their own logs
Their internal logs show:
Which sounds exactly like the kind of API-side failure you’d expect from a broken integration.
My questions
-
Is anyone else seeing Google contact sync failures in RingCentral?
-
Did Google change something recently with contacts API scopes?
-
Has anyone found a workaround?
-
Is this a known issue inside RingCentral?
At this point support just keeps deflecting to Google, but the evidence doesn’t really support that.
Would really appreciate any insight from other admins or anyone running RC + Google Workspace.