-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add service account json file to Auto-GPT.??? #1
Comments
Go to Google Cloud, enable the Google Analytics Reporting API, credentials > keys > Add Key > Create New Key > JSON, add this to the auto-gpt and rename it firebase.json. |
Guyssss would love some help please ! I keep getting User does not have sufficient permissions for this profile despite following all the steps. Command google_analytics returned: Error: <HttpError 403 when requesting https://analyticsreporting.googleapis.com/v4/reports:batchGet?alt=json returned "User does not have sufficient permissions for this profile.". Details: "User does not have sufficient permissions for this profile."> Here are the steps I have taken so far
Also, there are pull requests in my google analytics api , so there is evidence that the Firebase.json is working ? |
Make sure you added the email that's in firebase.json in your Google Analytics View Management. Did you also enable Google Reporting Analytics? |
I have added the email in the Firebase.json and granted it permission to google analytics. |
Try giving it the admin role instead of analyst. |
I
still the same after changing to admin role |
I can't seem to complete the installation of this plugin...I have successfully added youtube, twitter, and email...but this set of instructions appears to be for an advanced user of Google APIs and Analytics APIs.
What exactly doe this mean?
Add service account json file to Auto-GPT. What service account json file? I have the service account created, but I don't have clue about this json file it's asking, which causes it to fail execution.
Any input would be ideal.
The text was updated successfully, but these errors were encountered: