Best answer
Invalid username or password error in the app despite correct credentials
Best answer by SamB
Hey there
I’ll share the key details from Support’s replies here for anyone who comes across this with similar issues:
I can confirm the message you’re seeing ("This connection belongs to an inactive member”) means your Zap is still linked to an old or inactive RingCentral connection.
Here’s how we can get this fixed:
1. Confirm the correct app
Even though AgencyZoom may appear in the browser address bar, this Zap is using RingCentral. You’ll want to log in using your RingCentral credentials, not your AgencyZoom account, when reconnecting.
2. Reconnect RingCentral
- Visit https://zapier.com/app/connections/ringcentral
- Click + Add connection, then log in using your RingCentral username and password.
- Once reconnected, return to your Ring Sense Zap and select this new RingCentral connection in the first step.
3. Retest and publish
After updating the connection, test your RingCentral trigger again to confirm it connects successfully. Once the test passes, you should be able to publish and turn the Zap back on.
- Your RingCentral account connects in the trigger step (Step 1).
- Your AgencyZoom login details apply in the Webhook (POST) step, since that’s where data is being sent.
In Step 4 (the POST to the URL ending in /api/auth/login), you should use the AgencyZoom credentials that authenticate the API endpoint. You will not use your RingCentral credentials there.
If you’re unsure which API credentials or parameters AgencyZoom requires, their support team can confirm what information belongs in the Username, Password, or Header fields. You can find their API documentation here.
In short:
- Use RingCentral credentials for your RingCentral connection (Step 1).
- Use AgencyZoom credentials for your POST Webhook step (Step 4).
I’ll go ahead and mark this as the best answer since Support’s suggestions appear to have resolved things. If that’s not the case, or you run into any further issues just let us know. In the meantime, happy Zapping! ⚡
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.
+14- Zapier Orchestrator & Solution Partner
Hi
The Zap Run error indicates the app API being used in the Webhooks by Zapier Zap step has detected the un/pw is invalid, which would be related to invalid formatting for those data points.
DO NOT post your un/pw on public forums.
For us to have more context, we would need to see how your Zap step for the API request is configured.
+14- Zapier Orchestrator & Solution Partner
AgencyZoom API documentation for the endpoint being used: https://app.agencyzoom.com/openapi/#tag/Authentication/operation/Auth-Login
From the screenshot we can’t see the Headers.
Make sure to set this header:
- Content-Type: application/json
+6- Zapier Solution Partner
Hey
Try to use the SSO login authentication instead of the simple one to see if it fixes your authentication issue- https://app.agencyzoom.com/openapi/#tag/V4SSO-Authentication
Hope it helps!
- Zapier Staff
Hi
Were you able to give those tips a try? We’re here if you need more help or want to share how it went!
Nothing is working I'm putting in mu agency zoom password it says that's not it the gut i has built it out he no help and the systems says I'm an inactive member on my own account so i cannot make changes.
This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing personal or potentially sensitive details.
+11- Community Manager
- Answer
Hey there
I’ll share the key details from Support’s replies here for anyone who comes across this with similar issues:
I can confirm the message you’re seeing ("This connection belongs to an inactive member”) means your Zap is still linked to an old or inactive RingCentral connection.
Here’s how we can get this fixed:
1. Confirm the correct app
Even though AgencyZoom may appear in the browser address bar, this Zap is using RingCentral. You’ll want to log in using your RingCentral credentials, not your AgencyZoom account, when reconnecting.
2. Reconnect RingCentral
- Visit https://zapier.com/app/connections/ringcentral
- Click + Add connection, then log in using your RingCentral username and password.
- Once reconnected, return to your Ring Sense Zap and select this new RingCentral connection in the first step.
3. Retest and publish
After updating the connection, test your RingCentral trigger again to confirm it connects successfully. Once the test passes, you should be able to publish and turn the Zap back on.
- Your RingCentral account connects in the trigger step (Step 1).
- Your AgencyZoom login details apply in the Webhook (POST) step, since that’s where data is being sent.
In Step 4 (the POST to the URL ending in /api/auth/login), you should use the AgencyZoom credentials that authenticate the API endpoint. You will not use your RingCentral credentials there.
If you’re unsure which API credentials or parameters AgencyZoom requires, their support team can confirm what information belongs in the Username, Password, or Header fields. You can find their API documentation here.
In short:
- Use RingCentral credentials for your RingCentral connection (Step 1).
- Use AgencyZoom credentials for your POST Webhook step (Step 4).
I’ll go ahead and mark this as the best answer since Support’s suggestions appear to have resolved things. If that’s not the case, or you run into any further issues just let us know. In the meantime, happy Zapping! ⚡
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.