Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Problems with Google Apps Script API JavaScript "How to... Execute function"

Post

Problems with Google Apps Script API JavaScript "How to... Execute function"

+3
−0

As this is the first question about Google Apps Script, here is a very brief description: it is a platform that helps people easily get programmatic access to Google apps data like Gmail messages, Google Drive files, etc. and also to certain elements that can't be accessed through one of the Google APIs. It offers a web-based IDE and has its own API.

The Google Apps Script API docs include a quickstart section, having subsections for different languages / platforms including JavaScript.

I thoroughly reviewed the quickstart overview and the JavaScript subsection and got it to work, but when trying the "How too... Execute a function" I got stuck; more specifically, I'm getting 404 errors.

References:

This is my environment:

  • Google Workspace account. I'm the domain administrator.
  • New Google Cloud project, created following the quickstart instructions
  • New Google Apps Script project, created using the quickstart instructions

Hardware and Installed Software

  • Mac Mini Apple M1, MacOS Ventura 13.4.1.
  • Google Chrome
  • Visual Studio Code

Steps to reproduce the problem

  1. Read the links included above.
  2. Create the target script.
  3. Create the file from the JavaScript quickstart. Default name index.html.
  4. Create the file from the How to... Execute function. Default name index.js
  5. Modify index.html to load index.js.
  6. Modify index.html in such a way that instead of calling createScript() call callScriptFunction().
  7. Create the Google Cloud standard project.
  8. Enable the Apps Script API.
  9. In the API section of the Cloud project, go to credentials.
  10. Add the ApiKey. Take note of it.
  11. Add the Web client
  12. Add the allowed URI. If you will run this locally add http://localhost:8080.
  13. Create the OAuth consent screen
  14. Grab the Google Cloud project id and add it to the Google Apps Script project on Project settings.
  15. Deploy Google Apps Script as API executable
  16. Get the script Id.
  17. Add the ApiKey, Client Id to the index.html file.
  18. Add the script Id to the index.js file.
  19. Open index.html using Google Chrome.
  20. Click the button Authorize and follow the OAuth authorization flow.
  21. Open the Google Chrome DevTools Console.
    Here you will find the error message.
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Similar questions found elsewhere (1 comment)
Similar questions found elsewhere
Wicket‭ wrote over 1 year ago

Google Apps Script - call function deployed as API executable. This question was posted in December, it has one answer having a 0 score which refers to a linked webpage that is no longer available. I just have posted an answer, including a link to this question.