Deploy Apps Script PDF Conversion as a Web App
Deploying your conversion script as a web app gives your team a URL they can hit to trigger a PDF export. No one needs to open the Apps Script editor, and you control exactly who can access it.
Setting up the doGet or doPost function
Apps Script web apps respond to HTTP requests through doGet(e) and doPost(e) functions. A GET request with a document ID as a query parameter is the simplest interface: the web app receives the ID, runs the conversion, saves the PDF to Drive, and returns a JSON response with the Drive file URL.
Deployment settings
In the Apps Script editor, go to Deploy > New Deployment and choose Web app. Set Execute as to 'Me' so the script runs with your Drive permissions regardless of who calls it. Set Who has access to 'Anyone within your organization' to restrict it to your Workspace domain, or 'Anyone' for broader access.
Using the web app endpoint
After deployment, Apps Script gives you a URL. Make a GET or POST request to that URL with the required parameters. You can call it from a browser, from another script, from Zapier, or from any tool that can make HTTP requests. The web app handles the conversion and responds with the result.
Frequently Asked Questions
Can non-technical users trigger the web app?
Yes. Give them the URL and instructions. They can trigger it from a browser or you can build a simple form interface using HTML Service that presents a dropdown of available documents.
Is the web app secure?
Setting access to 'Anyone within your organization' restricts it to people signed into your Google Workspace domain. For public-facing endpoints, add your own authentication check inside the doGet/doPost function.
Related article
Set up a workflow to convert Google Docs to PDF →Ready to Try It?
Install the free Chrome extension and start converting your Google Docs to PDF in one click.
Install Free Extension