Google Scripts Login and Retreive Information From Website Updated FREE

Google Scripts Login and Retreive Information From Website

If you build a user interface for a script, yous tin can publish the script as a web app. For example, a script that lets users schedule appointments with members of a back up team would best be presented every bit a web app so that users can admission it directly from their browsers.

Both standalone scripts and scripts jump to Google Workspace applications tin can be turned into web apps, so long as they come across the requirements beneath.

Requirements for web apps

A script tin be published as a web app if it meets these requirements:

• It contains a doGet(e) or doPost(east) function.
• The function returns an HTML service HtmlOutput object or a Content service TextOutput object.

Request parameters

When a user visits an app or a program sends the app an HTTP Become request, Apps Script runs the function doGet(e). When a plan sends the app an HTTP POST request, Apps Script runs doPost(e) instead. In both cases, the eastward argument represents an issue parameter that tin incorporate data about whatsoever asking parameters. The structure of the event object is shown in the table below:

Fields
e.queryString	The value of the query string portion of the URL, or zero if no query cord is specified name=alice&north=ane&northward=2
east.parameter	An object of fundamental/value pairs that correspond to the request parameters. Only the first value is returned for parameters that take multiple values. {"name": "alice", "northward": "1"}
e.parameters	An object similar to e.parameter, but with an array of values for each primal {"name": ["alice"], "n": ["1", "2"]}
e.contextPath	Not used, ever the empty string.
e.contentLength	The length of the asking body for Post requests, or -1 for GET requests 332
eastward.postData.length	The aforementioned as due east.contentLength 332
e.postData.type	The MIME type of the Postal service body text/csv
e.postData.contents	The content text of the Mail service trunk Alice,21
e.postData.name	Always the value "postData" postData

For instance, you could pass parameters such as username and age to a URL as shown below:

          https://script.google.com/.../exec?username=jsmith&age=21                  

Then, you tin can brandish the parameters similar so:

          office doGet(e) {   var params = JSON.stringify(e);   return HtmlService.createHtmlOutput(params); }                  

In the above example, doGet(e) returns the following output:

          {   "queryString": "username=jsmith&age=21",   "parameter": {     "username": "jsmith",     "age": "21"   },   "contextPath": "",   "parameters": {     "username": [       "jsmith"     ],     "age": [       "21"     ]   },   "contentLength": -i }                  

Deploy a script every bit a web app

To deploy a script equally a web app, follow these steps:

New editor

1. At the top right of the script project, click Deploy > New deployment.
2. Side by side to "Select type," click Enable deployment types > Spider web app.
3. Enter the data near your spider web app in the fields under "Deployment configuration."
4. Click Deploy.

Legacy editor

1. Save a new version of the script by selecting File > Manage Versions, so Relieve New Version.
2. Select Publish > Deploy equally spider web app.
3. Under Project version, select the version you just saved.
4. Under Execute the app as, select whose authorization the app should run with: your account (the programmer'south) or the account of the user who visits the app (come across permissions).
5. Under Who has access to the app, select who should be allowed to visit it. The options differ depending on the type of business relationship you lot take, merely they tin can include "Only myself", whatsoever member of your domain, "Anyone" (with a Google business relationship), or "Anyone, even bearding".
6. Click Deploy.

Subsequently y'all deploy your web app, the dialog that confirms your deployment and provides the deployed URL. This URL ends in /exec and is for the deployed version of your app, based on the concluding version you saved and deployed.

You can share the web app URL with those you would like to use your app, provided you take granted them admission.

Test a web app deployment

New editor

To test your script equally a spider web app, follow the steps beneath:

1. At the pinnacle right of the script projection, click Deploy > Test deployments.
2. Next to "Select blazon," click Enable deployment types > Spider web app.
3. Nether the web app URL, click Copy.
4. Paste the URL in your browser and test your web app.

This URL ends in /dev and can but be accessed by users who have edit access to the script. This case of the app ever runs the most recently saved code and is but intended for testing during development.

Legacy editor

Later you lot deploy your web app, the dialog that confirms your deployment provides a link to test your latest code.This URL ends in /dev and can only be accessed by users who take edit admission to the script. This instance of the app always runs the most recently saved code — not necessarily a formal version — and is intended for testing during development.

Permissions

The permissions for a web app differ depending how you choose to execute the app:

• Execute the app every bit me—In this instance, the script e'er executes as y'all, the owner of the script, no matter who accesses the web app.
• Execute the app every bit user accessing the web app—In this case, the script runs nether the identity of the agile user using the web app. This permission approach causes the web app to show the email of the script owner when the user authorizes access.

Embedding your spider web app in Google Sites

You tin besides embed web apps in both the classic and new versions of Google Sites.

Embedding a web app in new Sites

In order to embed a web app, it must first be deployed. You likewise need the Deployed URL from the Deploy dialog.

To embed a web app into a new Sites page, follow these steps:

1. Open up the Sites folio where you'd like to add the spider web app.
2. Select Insert > Embed URL.
3. Paste in the web app URL and and so click Add.

The spider web app appears in a frame in the page's preview. When you lot publish the page, your site viewers may demand to authorize the spider web app before it executes normally. Unauthorized web apps present authorization prompts to the user.

Embedding a web app in classic Sites

You can bind a script to a archetype Google Site in much the aforementioned way as a you can bind a script to a Google Doc or Canvas. To create a jump script, visit your site, click the gear icon , so select Manage site. On the Manage Site folio, click Apps Scripts in the left nav, then the Add new script button. This opens a new script in the Apps Script editor, where you can code and deploy your web app.

You can too embed your web app in a page. You can bind the web app to the Site or you can use any web app that you have the URL for. To embed a spider web app into a Google Sites folio, follow the steps below:

1. Open an existing Site for which yous have edit access or create a new Site.
2. Navigate to the folio in your Site where you want to embed the web app.
3. Click the edit icon, and and then Insert > Google Apps Script.
4. Choose the script from the list that represents your spider web app. If your spider web app is not bound to this Site, y'all tin can paste in the web app URL instead.
5. Click the Select button, choose the desired options from the adjacent dialog, and click Save.
6. Salve your changes to the page and then you should see your spider web app embedded in your Sites folio.

Web Apps and Browser History

It can be desirable to have an Apps Script web app simulate a multi-folio application, or ane with a dynamic UI controlled via URL parameters. In order to do this well, y'all can define a country object to stand for the app's UI or page, and push the state into the browser history as the user navigates your app. Y'all tin can besides mind to history events and so that your web app displays the correct UI when the user navigates back and along with the browser buttons. By querying the URL parameters at load time, you tin can have your app dynamically build its UI based on those parameters, assuasive the user to start the app in a particular state.

Apps Script provides two asynchronous client-side JavaScript APIs to assist with creating web apps that are linked to the browser history:

• google.script.history provides methods to allow dynamic response to browser history changes. This includes: pushing states (simple Objects you can ascertain) onto the browser history, replacing the height state in the history stack, and setting a listener callback function to answer to history changes.

• google.script.url provides the means to retrieve the current page'south URL parameters and URL fragment, if they are present.

These history APIs are only available to web apps. They are not supported for sidebars, dialogs or add-ons. This functionality is also non recommended for use in spider web apps embedded in a Google Sites.

Google Scripts Login and Retreive Information From Website

DOWNLOAD HERE

Source: https://developers.google.com/apps-script/guides/web

Posted by: jennaquithethand.blogspot.com