├── LICENSE ├── README.md ├── assets ├── image_0.png ├── image_1.png ├── image_10.png ├── image_11.png ├── image_2.png ├── image_3.png ├── image_4.png ├── image_5.png ├── image_6.png ├── image_7.png ├── image_8.png └── image_9.png └── src ├── appsscript.json ├── code.gs └── index.js /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "{}" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright {yyyy} {name of copyright owner} 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Cloud Functions for Firebase in Google Apps Script 2 | *This tutorial was developed by [Riël Notermans](https://developers.google.com/experts/people/ri-l-notermans) and [Martin Hawksey](https://developers.google.com/experts/people/martin-hawksey) GDEs for Google Apps Script. This tutorial is based on a supporting video featuring Riël going through and explaining each of these steps [https://www.youtube.com/watch?v=yi5ktHjv_FE](https://www.youtube.com/watch?v=yi5ktHjv_FE)* 3 | 4 | Google Apps Script is a powerful tool to integrate with Google products and third party services. As Apps Script is a free service which runs on Google servers there are quotas designed to prevent abuse of the service. These quotas can however sometimes prevent you from completing your project. In this tutorial we introduce Cloud Functions for Firebase as a solution for getting around some of the quota limits. In particular, we look at how you can get around issues when trying to fetch files greater than 10MB. In this tutorial we show how a Cloud Function can be used with Google Apps Script to fetch a large file, save it to your Google Drive and return a file id which can be used in the rest of your script project. 5 | 6 | >**Important:** In this tutorial as we are using a cloud function to make an external HTTP request which is not included in the Firebase Spark Free plan. We recommend upgrading your Firebase project to the Blaze Pay as you go plan. Given the requested file size in this tutorial the current estimated cost for each execution depends mostly on the outbound traffic in this case, which is 20Mb. Inbound (google services) do not count, so only the fetch. Pricing is about 0.25 cents on the Blaze plan for one execution. If you haven’t used Google Cloud before you can [get $300 of free credit for 12 months](https://cloud.google.com/free/). If you are scared that you might do something wrong and create a loop, using loads of data, then in the Google Cloud platform you can set your maximum billing to $0. Here is more information on current [Firebase Pricing](https://firebase.google.com/pricing/). 7 | 8 | **Note:** In this tutorial we are using Cloud Functions for Firebase. Cloud Functions for Firebase are essentially a wrapper around Google Cloud Functions, designed to make it easier to use and integrate these within your Firebase project and integrate with other Firebase services. If you are just using functions you might consider using Google Cloud Functions instead. 9 | 10 | ## Setting up and creating a Cloud Function for Firebase 11 | 12 | 1. Start a new script project [https://script.google.com/](https://script.google.com/) 13 | 14 | 2. In the Script Editor open Resources > Cloud Platform project… 15 | 16 | 3. In the dialog that opens click on the link under the ‘This script is currently associated with project:’ prompt. 17 | 18 | 4. In the Google Developer Console window that opens click on the menu icon in the top left (![image alt text](assets/image_0.png)) and then click the Google Cloud Platform link from the bottom of the menu. [You can also avoid steps 1-4 to get directly to the Google Cloud Platform by visiting [https://console.cloud.google.com](https://console.cloud.google.com)] 19 | 20 | 5. In the Google Cloud Platform window that open click the Activate Google Cloud Shell![image alt text](assets/image_1.png) 21 | 22 | 6. Open the Firebase Console at [https://console.firebase.google.com/](https://console.firebase.google.com/) and create a new project (as noted at the start of this tutorial you'll need to modify your project to one of the paid plans - we recommend the Blaze Pay as you go for this tutorial). 23 | 24 | 7. In the new project click ‘Functions’ from the left side menu and then click ‘Get Started’. 25 | 26 | 8. In the window that opens copy the command `npm install -g firebase-tools` to the Google Cloud Shell window opened in step 5. (running this command also updates to the latest version)![image alt text](assets/image_2.png)![image alt text](assets/image_3.png) 27 | > NPM = Node Package Manager. If you wonder what it has to do with Cloud Functions for Firebase, let us explain. Functions run in the Node.js environment, just like Apps Script runs in the Apps Script environment. To add modules in Node scripts, you use npm to install them. NPM makes sure all libraries get installed or updated, and will update your package.json to let the node environment know what modules are used. When you upload a function, you upload the installed modules as well (actually you upload the whole functions directory). The package.json file tells the environment what modules are installed. 28 | > 29 | > The most common commands: 30 | > 31 | >**`npm install`** 32 | >Reads package.json and installs all modules listed there. This is easy if you use someone else's function and need to install all modules that are needed. 33 | > 34 | >**`npm install packagename`** 35 | >Install a separate package. Be alert: this does not update package.json! 36 | > 37 | >**`npm install packagename@version`** 38 | >Install a specific version of a separate package. Be alert: this does not update package.json! 39 | > 40 | >**`npm install packagename --save`** 41 | > Install a package and update package.json as well. This is what you usually do when writing your own cloud function. 42 | 43 | 9. It will take 1-2 minutes to install the Firebase tools and some errors may be thrown but these can be ignored for this tutorial. 44 | 45 | 10. When it finishes still in the Google Cloud Shell window now type `firebase login --no-localhost`. If this is your first Firebase project you will need to follow the command prompts copy/pasting the authentication url into a new browser tab and once logged in and authenticated the authorisation code back into the Google Cloud Shell window. Once completed you should see a `Success! Logged in as …` message![image alt text](assets/image_4.png) 46 | 47 | 11. In the shell make a project directory with mkdir cfdemo and then change directory cd cfdemo. 48 | >Cloud Shell gives you a 5GB home directory which persist across sessions. Here is [more information on Cloud Shell. ](https://cloud.google.com/shell/) 49 | 50 | 12. To initiate Cloud Functions in our project now enter the command `firebase init` and use your down cursor to Functions: Configure and deploy Cloud Functions and **press your spacebar to select before pressing enter**. [You can also use `firebase init functions` to skip the selection step] ![image alt text](assets/image_5.png) 51 | 52 | 13. You will now be prompt to select the Firebase project, at which point you can use your down cursor to select the project you created earlier. 53 | 54 | 14. You will be asked if you `want to install dependencies with npm now?`, select `Y`. This will install all packages for Node.js that are needed for functions to work. 55 | 56 | 15. At the top of the Google Cloud Shell window click on the Files menu to allow you to launch the code editor![image alt text](assets/image_6.png) 57 | 58 | 16. In the code editor open the `index.js` file in the `functions` directory![image alt text](assets/image_7.png) 59 | 60 | 17. Copy and paste the [code from this repo](https://github.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/blob/master/src/index.js) to replace the contents of `index.js` 61 | 62 | 18. The code includes a number of required libraries. To include these hover/click over the ![image alt text](assets/image_8.png) icons and select ‘Update package.json’. [To install these packages from the Cloud Shell you can also `cd functions` and use the command `npm install googleapis google-auth-library request --save` (using the `--save` option to make sure `package.json` gets updated] ![image alt text](assets/image_9.png) 63 | 64 | 19. Back in the Cloud Shell change directory to functions with `cd functions` 65 | 66 | 20. To install the required modules enter the command `npm install` 67 | 68 | 21. To deploy our function `firebase deploy --only functions` 69 | 70 | To call our cloud function from Google Apps Script in the Google Apps Script Editor enter: 71 | 72 | function fetchFromFirebaseFunctions() { 73 | // DriveApp.getRootFolder() included to make sure the scope is added to the project so that our 74 | // token can be passed to the firebase function (this is obsolete as we call DriveApp later in the code) 75 | DriveApp.getRootFolder(); 76 | 77 | var url = "https://upload.wikimedia.org/wikipedia/commons/e/e6/Clocktower_Panorama_20080622_20mb.jpg"; 78 | var fnUrl = "https://us-central1-cloudfunctionsdemo-2230.cloudfunctions.net/answerTheFetch"; 79 | 80 | var resp = JSON.parse(UrlFetchApp.fetch(fnUrl+"?url="+url+"&token="+ScriptApp.getOAuthToken()+"&filename=image.jpg").getContentText()); 81 | var file_loaction = DriveApp.getFileById(resp.id).getUrl(); 82 | 83 | Logger.log("The file "+resp.id+" can be viewed at "+file_loaction); 84 | } 85 | 86 | When the script is run you will be prompted for one time authorisation and when it finishes you should be be able to open View > Logs and see the Google Drive url for the copied image. 87 | 88 | ## Summary 89 | 90 | Congratulations you've just deployed and used your first Cloud Function for Firebase. This is a basic example to get you started with Cloud Functions for Firebase and there are a number of enhancements to this example you might want to use if using cloud functions in your Google Apps Script projects. For example, there are a number of improvements upi could make in error handling. It should also be noted that currently there is no way to restrict execution of a cloud function by for example domain whitelisting. It is possible to include your own authentication or passkey access within your cloud function remembering that with reject access a small amount of resource allowance will be used. As Firebase provides an authentication service you might want to look at this as an option. If using a cloud function within a add-on or webapp you might find [this example code](https://github.com/firebase/functions-samples/tree/master/authorized-https-endpoint) useful. 91 | 92 | 93 | -------------------------------------------------------------------------------- /assets/image_0.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_0.png -------------------------------------------------------------------------------- /assets/image_1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_1.png -------------------------------------------------------------------------------- /assets/image_10.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_10.png -------------------------------------------------------------------------------- /assets/image_11.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_11.png -------------------------------------------------------------------------------- /assets/image_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_2.png -------------------------------------------------------------------------------- /assets/image_3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_3.png -------------------------------------------------------------------------------- /assets/image_4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_4.png -------------------------------------------------------------------------------- /assets/image_5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_5.png -------------------------------------------------------------------------------- /assets/image_6.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_6.png -------------------------------------------------------------------------------- /assets/image_7.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_7.png -------------------------------------------------------------------------------- /assets/image_8.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_8.png -------------------------------------------------------------------------------- /assets/image_9.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mhawksey/Cloud-Functions-for-Firebase-in-Google-Apps-Script/677288561922b6c02c7feb73415d1fb1c954c239/assets/image_9.png -------------------------------------------------------------------------------- /src/appsscript.json: -------------------------------------------------------------------------------- 1 | { 2 | "timeZone": "Europe/London", 3 | "dependencies": { 4 | }, 5 | "exceptionLogging": "STACKDRIVER" 6 | } 7 | -------------------------------------------------------------------------------- /src/code.gs: -------------------------------------------------------------------------------- 1 | function fetchFromFirebaseFunctions() { 2 | // DriveApp.getRootFolder() included to make sure the scope is added to the project so that our 3 | // token can be passed to the firebase function (this is obsolete as we call DriveApp later in the code) 4 | DriveApp.getRootFolder(); 5 | 6 | var url = "https://upload.wikimedia.org/wikipedia/commons/e/e6/Clocktower_Panorama_20080622_20mb.jpg"; 7 | var fnUrl = "https://us-central1-cloudfunctionsdemo-2230.cloudfunctions.net/answerTheFetch"; 8 | 9 | var resp = JSON.parse(UrlFetchApp.fetch(fnUrl+"?url="+url+"&token="+ScriptApp.getOAuthToken()+"&filename=image.jpg").getContentText()); 10 | var file_loaction = DriveApp.getFileById(resp.id).getUrl(); 11 | 12 | Logger.log("The file "+resp.id+" can be viewed at "+file_loaction); 13 | } 14 | -------------------------------------------------------------------------------- /src/index.js: -------------------------------------------------------------------------------- 1 | // The Cloud Functions for Firebase SDK to create Cloud Functions and setup triggers. 2 | const functions = require('firebase-functions'); 3 | 4 | const admin = require('firebase-admin'); 5 | admin.initializeApp(functions.config().firebase); 6 | 7 | // Google APIs client library used to call Google Drive 8 | var google = require('googleapis'); 9 | 10 | // Google Auth Library for Node.js 11 | var googleAuth = require('google-auth-library'); 12 | 13 | // Request is designed to be the simplest way possible to make http calls 14 | var request = require('request'); 15 | 16 | // our cloud function 17 | // Takes a url, token and filename and fetches the file adding to Google Drive returning the file id 18 | // More info on HTTP Triggers https://firebase.google.com/docs/functions/http-events 19 | exports.answerTheFetch = functions.https.onRequest((req, res) => { 20 | 21 | var token = req.query.token; 22 | var filename = req.query.filename || "temp_file"; 23 | 24 | // writing to the Firebase log https://firebase.google.com/docs/functions/writing-and-viewing-logs 25 | console.log(filename); 26 | 27 | // handling auth to write file to Drive 28 | var auth = new googleAuth(); 29 | var oauth2Client = new auth.OAuth2(); 30 | oauth2Client.setCredentials({ 31 | access_token: token 32 | }); 33 | 34 | // setting Drive access 35 | var drive = google.drive('v3'); 36 | 37 | var media = { 38 | body: request(req.query.url) //stream! 39 | }; 40 | 41 | // create file on Drive 42 | drive.files.create({ 43 | resource: {'name': filename}, 44 | media: media, 45 | fields: 'id', 46 | auth: oauth2Client 47 | }, function(err, file) { 48 | if (err) { 49 | // Handle error 50 | console.log(err); 51 | res.send(err); 52 | } else { 53 | res.send(JSON.stringify({ 54 | id: file.id 55 | })); 56 | } 57 | }); 58 | }); --------------------------------------------------------------------------------