You can use Next Matter integration steps to directly integrate your workflow with Google Drive to, for example, upload files.
Where is the file / document ID in Google
https://docs.google.com/document/d/143uVKzah2WhnPEHY3ATwM4UM0K-hjvZ3OB_kT93qrQU/edit
https://drive.google.com/drive/u/0/folders/FOLDER_ID
Key | Type | Value |
---|---|---|
metadata | text | {"name": "{data reference to the filename of the uploaded file}", "parents":["GDRIVE_FOLDER_ID"]} |
key1 | file | {data reference to the "First File" field from the file upload step} |
https://www.googleapis.com/upload/drive/v3/files?uploadType=multipart
fileid
reference of the value $id.
https://www.googleapis.com/drive/v2/files/FILE_ID/permissions?supportsAllDrives=true&includeTeamDriveItems=true&includeItemsFromAllDrives=true
application/json
fileid
reference of the value $id.
https://www.googleapis.com/drive/v3/filesFILEID_OF_THE_FILE_TO_COPY/copy?supportsAllDrives=True
application/json
fileid
reference of the value $id.
https://drive.google.com/drive/u/0/folders/FOLDER_ID
. The parent folder is the folder in which you’re creating a sub-folder.application/json
folderid
reference of the value $id.
https://www.googleapis.com/drive/v3/files/FILE_ID?addParents=FOLDER_ID
application/json
Key | Type | Value |
---|---|---|
metadata | text | {"name": "{data reference to the filename of the uploaded file}"} |
key1 | file | {data reference to the uploaded file} |
https://www.googleapis.com/upload/drive/v3/FILE_ID
fileid
reference of the value $id.