I’m trying to send this to the support team and I’m not sure if this is the right place.
I tried doing the first tutorial and after ensuring I connected successfully to Google sheets it still fails. I did accidentally upgrade the Google sheets node to v15 maybe that was it (from v9)
Product feedback
when things fail Gumloop needs to do a lot better job at exposing the failure. These messages “Google Sheets Writer Failed!” are basically useless and most users would abandon Gumloop entirely at this point
Agents on other platforms I use observe the output and make changes until things are fixed unless human input was absolutely necessary. It’d be cool if Gummie did this; in fact, I’d be so bold as to say having an agent to help manage the agent flows itself will become table stakes REAL soon now as many others offer it.
Hey @julian - It seems like the the account you’ve authenticated with doesn’t have the necessary permission to view or edit the Google Sheet at ID “1B4EB-bt7gcMHM92-29TseibMaer0iswJO77EngomOTA”
To resolve this:
Check that the Google account being used has been granted access to this specific spreadsheet
Verify the sharing settings of the spreadsheet (need to be set to “Anyone with the link” or specifically shared with the account that’s making the request)
If the above options don’t work try revoking your credentials here and then authenticating again. Once you’ve done that please delete the Google Sheet node and add it back from the node library.
If these options don’t work please share the latest run link after doing the changes.
Your feedback makes total sense! Improving error messages is definitely on the roadmap. Some errors can’t be resolved within the workflow or might be confusing for users, so finding the right balance is tricky. That said, we’re working on making error messages clearer and giving Gummie more context on the flow so it can assist better in these situations.
As you can see, Gumloop has full access through oauth so “Anyone with access” should not be necessary. However indeed changing privileges to “Anyone with the link” / Write did work.
