What is your goal?
Hi @vendy 
,
First, thank you again for your help during the review process — myCRMSIM was approved on 29 May and is now live in the Make app library. Really appreciate the team’s support 
I’m reaching out because after release I discovered an issue affecting public users, and I need a developer assigned so the patch can be reviewed and pushed live.
The issue (for public users):
When new public users try to create a myCRMSIM connection in any scenario, they receive this error from our backend:
client_id and redirect_uri are required
After investigation, I found that the Common Data values (clientId, clientSecret) we configured during the original review do not appear to be passed through to public users — they resolve to empty strings on the user side, so the OAuth authorize request fails at our backend before login.
For me (the app owner / dev workspace), the connection works fine because my dev environment has access to Common Data. So the issue is only visible to public users in the marketplace.
The fix (already applied in my dev workspace):
I moved the clientId and clientSecret directly into the Connection Communication code (in the authorize qs and the token/refresh Basic auth header), replacing the {{common.clientId}} and {{common.clientSecret}} references. No other behavior, scope, or endpoint changes — only credential resolut
What is the problem & what have you tried?
Hi @vendy ,
First, thank you again for your help during the review process — myCRMSIM was approved on 29 May and is now live in the Make app library. Really appreciate the team’s support
I’m reaching out because after release I discovered an issue affecting public users, and I need a developer assigned so the patch can be reviewed and pushed live.
The issue (for public users):
When new public users try to create a myCRMSIM connection in any scenario, they receive this error from our backend:
client_id and redirect_uri are required
After investigation, I found that the Common Data values (clientId, clientSecret) we configured during the original review do not appear to be passed through to public users — they resolve to empty strings on the user side, so the OAuth authorize request fails at our backend before login.
For me (the app owner / dev workspace), the connection works fine because my dev environment has access to Common Data. So the issue is only visible to public users in the marketplace.
The fix (already applied in my dev workspace):
I moved the clientId and clientSecret directly into the Connection Communication code (in the authorize qs and the token/refresh Basic auth header), replacing the {{common.clientId}} and {{common.clientSecret}} references. No other behavior, scope, or endpoint changes — only credential resolution.
This is the only change in this update.
What I’ve done so far:
Updated the Connection Communication code in the Make platform- Make’s UI shows: “Changes are only effective in your account. To apply these changes globally, go to the Review tab and submit the app for review.”
- Submitted the changes for review via the Review tab
- Sent an email to Levs B explaining the patch
Reviewer field currently shows “TBS” (To Be Assigned)
My request:
Could a developer please be assigned to review this small patch? Public users are currently blocked from creating new connections, so a quick turnaround would be hugely appreciated.
I’m happy to:
- Provide more technical details or screenshots
- Make adjustments if there’s a preferred way to keep Common Data while still passing it to public users
- Hop on a call if helpful
Reference details:
- App: myCRMSIM [v1.0.0]
- Case ID: 2099406:2082001
- Original reviewer: Levs B
- Approval date: 29 May 2026
- Patch submission date: [TODAY’S DATE]
- Public API docs: https://documenter.getpostman.com/view/50634098/2sBXwjvZ7m
Thanks so much for your help, Vendy!
Kind regards,
Gary Capps
