I have connected all my apps in my scenario but this error is popping up?
The operation failed with an error. 403: PERMISSION_DENIED - The caller does not have permission
Welcome to the Make community!
We’d love to help, however, you have not provided sufficient information to demonstrate the problem that would allow us to reproduce the scenario and any issue/s and/or error/s.
To allow others to assist you with your scenario, please provide the following:
1. All Relevant Screenshots
We need to see what you’re working with to give you the best advice. It would help by having screenshots of:
- the full scenario,
- any error messages,
- individual module fields,
- relevant filter settings (conditions), and
- module output bundles
- external services (spreadsheet headers, sample data, etc.)
You can upload images here using the Upload icon in the text editor:
We would appreciate it if you could upload screenshots here instead of linking to them outside of the forum. This allows us to zoom in on the image when clicked, and avoid tracking cookies from third-party websites.
2. Scenario Blueprint
Please export the scenario blueprint. Providing your scenario blueprint file will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return - this would greatly benefit you in implementing our suggestions as you can simply paste module exports back into your scenario editor!
To export your scenario blueprint, click the three dots at the bottom of the editor then choose ‘Export Blueprint’.
You can upload the file here by clicking on this button:
3. Module Output Bundles
Please provide the output bundles of each of the relevant modules by running the scenario (you can also get this without re-running your scenario from the History tab).
Click on the white speech bubbles on the top-right of each module and select “Download input/output bundles”.
A. Upload as a Text File
Save each bundle contents in a plain text editor (without formatting) as a bundle.txt file.
You can upload the file here by clicking on this button:
B. Insert as Formatted Code Block
If you are unable to upload files on this forum, alternatively you can paste the formatted bundles.
Here are some ways to provide text content in a way that it won’t be modified by the forum.
-
Method 1: Type code fence manually —
Add three backticks```before and after the content/bundle, like this,```
content goes here
``` -
Method 2: Highlight and click the format button in the editor —
-
Method 3: Upload your file and share the public link —
(this method is only recommended for large files exceeding the forum upload limit)
Providing the input/output bundles will allow others to replicate what is going on in the scenario, especially if there are complex data structures (nested arrays and collections) or if external services are involved, and help you with mapping the raw property names from collections.
Sharing these details will make it easier for others to assist you.
Sam,
I read your previous instructions. The operation failed with an error. 403: PERMISSION_DENIED - The caller does not have permission. I have shown below the editable link to the scenario I’m creating. Also below is the module output bundles and the JSON file of the oracle predictions scenario I was creating. Please let me know how to fix the error. Thanks
scenario-2197030-logs.csv (5.2 KB)
Oracle predictions automation (1).json (423.5 KB)
https://us2.make.com/782044/scenarios/2197030/edit
We cannot open your link, because we aren’t in your Make team.
Please provide screenshots as well, thank you.
Here is the screenshots of the error I get when I click run on the YT videos comments analyzer oracle 300 scenario.
The 403 error attached below has an open log button inside of it.
Whenever I click run scenario the 403 error stating permission denied comes up and goes away before I cans screen shot it on the same pic.
Based on your screenshots, it appears that the connection for your Sheets module does not have sufficient scopes to read from the file.
Could you follow these instructions again to ensure you did not miss any steps, including adding all the scopes?
How to Connect and Use Google APIs in Make!
0. Prerequisites
-
0.1. You need to have a Google account
Make sure you can sign in to Google Cloud Console with this.
-
0.2. Create a Google Cloud Platform (GCP) project
Follow this main help centre guide on How to set up a custom OAuth 2.0 custom app in Make.
1. Enable Google APIs
-
1.1. Enable the relevant APIs that you want to use
Search for the relevant Google API here: https://console.cloud.google.com/apis/library
2. OAuth Client
Direct Link: https://console.cloud.google.com/apis/credentials
-
2a. Create “OAuth client ID” Credentials
-
2b. Insert all the Google Redirect URIs for your app
Insert All Google Redirect URIs
Here are some commonly-needed redirect URIs you need for your Google Cloud Console OAuth app. If you set these up, you can reuse the same GCP app for other Google apps and modules on Make.
https://www.make.com/oauth/cb/oauth2 https://www.make.com/oauth/cb/google https://www.make.com/oauth/cb/google/ https://www.make.com/oauth/cb/google-custom https://www.make.com/oauth/cb/google-restricted https://www.make.com/oauth/cb/google-cloud-speech https://www.make.com/oauth/cb/google-search-console https://www.make.com/oauth/cb/google-analytics-4 https://www.make.com/oauth/cb/google-ads2 https://www.make.com/oauth/cb/google-ads2/ https://www.make.com/oauth/cb/youtube https://www.make.com/oauth/cb/chromeIncluding These Google Redirect URIs
You are also required to insert the legacy URLs below from the old Integromat system that not been migrated to Make yet (same as the above list, but replace “make” with “integromat”):
https://www.integromat.com/oauth/cb/oauth2 https://www.integromat.com/oauth/cb/google https://www.integromat.com/oauth/cb/google/ https://www.integromat.com/oauth/cb/google-custom https://www.integromat.com/oauth/cb/google-restricted https://www.integromat.com/oauth/cb/google-cloud-speech https://www.integromat.com/oauth/cb/google-search-console https://www.integromat.com/oauth/cb/google-analytics-4 https://www.integromat.com/oauth/cb/google-ads2 https://www.integromat.com/oauth/cb/google-ads2/ https://www.integromat.com/oauth/cb/youtube https://www.integromat.com/oauth/cb/chromeNote 1: Due to inconsistencies in Make’s implementation of the connections, there are two separate entries where has one is
googleand another ending in a forward slashgoogle/- you might need one or the other, so we have to use both!Note 2: Once you’ve set these up, you can use/reuse the same Google OAuth App ID + Secret for all the supported Google connections and modules on Make - you’ll just have to enable the relevant Google APIs!
3. OAuth consent screen
Direct Link: https://console.cloud.google.com/apis/credentials/consent/edit
-
3a. Insert Two Authorised Domains
-
Insert
make.comandintegromat.com -
Fill in other required fields
-
Click “Save and Continue”.
-
-
3b. Add All Scopes
-
Click “Add or Remove Scopes”
-
Select 100 “Rows per page”, for each page, check all the rows, OR
-
Manually type in the scopes you need
-
Click “Update” at the bottom
-
-
3c. Step through and go to dashboard
At the last step/page, click “BACK TO DASHBOARD” instead of “Prepare for Verification”
-
3d. Publish your GCP OAuth2 app
You will need to set your OAuth application to “Production”, otherwise the credentials expire very frequently.
-
To do this, go back to “OAuth consent screen”
-
Then click the “PUBLISH APP” button
-
Then click the “CONFIRM” button
-
4. Create New Connection (HTTP, or respective Google module)
You can find the Client ID and Client Secret in the OAuth2 app you created in GCP, on the right-hand side of where you inserted the callback URLs in step 2:
-
4a. Specific Google module (Sheets, Docs, Drive, Gmail, etc.)
Insert the GCP app client ID and secret here BEFORE clicking “Sign in”
(Gmail example)
OR,
-
4b. HTTP OAuth 2.0 Request module
You need a “Authorize Parameters” key of
redirect_uriwith the above Make OAuth2 callback URL.
Related Topics:
Hope this helps! Let me know if there are any further questions or issues. P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!
— @samliew
For more information, also see these similar questions by other community members, which may answer your question in further detail:
- 403: PERMISSION_DENIED - The caller does not have permission Tried both personal and workspace gmail accounts
- The operation failed with an error. 403: PERMISSION_DENIED - The caller does not have permission
- 403: PERMISSION_DENIED - The caller does not have permission
- Google forms - The operation failed with an error. 403: PERMISSION_DENIED - The caller does not have permission
Do try to search this forum for existing answers, and also use the documentation in the Help Centre. You are likely to get to a solution faster this way and also help keep the forum organised. Thanks for your cooperation!
Hope this helps! Let me know if there are any further questions or issues. P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!
— @samliew