This topic was automatically generated from Slack. You can find the original thread here.
I’m using the Pipedream Connect feature for Zoom integration. I created an application in the Zoom Marketplace and copied all the credentials into a new OAuth Zoom client, but for some reason, I always get a 400 Bad Request error when I try to connect the Zoom account.
It sounds like you’re running into a 400 Bad Request error when trying to connect your Zoom account to Pipedream Connect using your own Zoom OAuth app credentials. Here are some common causes and troubleshooting steps: ## Common Causes of 400 Bad Request with Zoom OAuth 1. Redirect URI Mismatch - Zoom requires that the redirect URI you configure in your Zoom Marketplace app matches exactly with the redirect URI Pipedream uses. - Double-check that the redirect URI you entered in the Zoom Marketplace matches the one provided by Pipedream when you set up your OAuth client. - Even a small typo or missing slash can cause a 400 error. 2. Incorrect Client ID or Secret - Ensure you copied the Client ID and Client Secret exactly from the Zoom Marketplace app to Pipedream. - Watch for extra spaces or missing characters. 3. App Not Activated or Published - Make sure your Zoom app is activated in the Zoom Marketplace. If it’s in development mode, ensure it’s allowed to be used for OAuth. 4. Scopes Not Set Properly - Make sure the scopes you request in Pipedream match what’s configured in your Zoom app. 5. Account Type - Some Zoom OAuth features require a paid account or specific permissions. ## Steps to Troubleshoot 1. Check Redirect URI - In the Zoom Marketplace, go to your app → “OAuth” section → “Redirect URL for OAuth” and “Add Allow List”. - Copy the exact redirect URI from the Pipedream OAuth client setup and paste it into both fields in Zoom. 2. Verify Credentials - Re-copy the Client ID and Client Secret from Zoom to Pipedream, ensuring no extra spaces. 3. Check App Status - Ensure your Zoom app is activated and not restricted to test users unless you’re testing with an allowed account. 4. Check for Error Details - Sometimes Zoom’s error page will give more details about what’s wrong (e.g., invalid redirect URI). 5. Try Re-creating the OAuth Client - If all else fails, try deleting and re-creating the OAuth client in Pipedream and/or the Zoom app. ## Additional Support If you continue to have trouble after checking these items, please visit Support - Pipedream for more support options. You can also provide screenshots (with sensitive info redacted) to help the team diagnose the issue. — Summary: A 400 Bad Request error is most often caused by a mismatch in the redirect URI or incorrect client credentials. Double-check these settings in both Zoom and Pipedream. If you’re still stuck, reach out to Pipedream support for direct help.
Hey, can you let me know your workspace ID?
glossapro1
Can you try adding the user:read:user scope to your OAuth configuration in Zoom?
Thank you very much, it works, but when i strip all the other scopes. it seems the problem lays in cloud_recording:read:recording and meeting:read:meeting scopes.
