Google Drive

Upload files, create folders, and manage content in Google Drive. In Appbricx, your workflows and server functions call it by name once it is connected.

What you can do

16 actions, each one call from a workflow or a server function. Triggers come from your app: a row changing, a schedule or a webhook.

  • List fileslist-files
    List files from a Google Drive folder
  • Read File Contentread-file
    Read a selected file from google drive file
  • Searchsearch-folder
    Search a Google Drive folder for files/sub-folders
  • Create new filecreate_new_gdrive_file
    Create a new text file in your Google Drive from text
  • Create new foldercreate_new_gdrive_folder
    Create a new empty folder in your Google Drive
  • Delete filedelete_gdrive_file
    Delete permanently a file from your Google Drive
  • Delete permissionsdelete_permissions
    Removes a role from an user for a file or folder
  • Duplicate Fileduplicate_file
    Duplicate a file from Google Drive. Returns the new file ID.
  • Get File Informationget-file-or-folder-by-id
    Get a file folder for files/sub-folders
  • Move Filegoogle-drive-move-file
    Moves a file from one folder to another.
  • Save Document as PDFsave_file_as_pdf
    Save a document as PDF in a Google Drive folder
  • Set public accessset_public_access
    Set public access for a file or folder

All 16 actions with their inputs

Set it up

About two minutes, once per project or once for the whole workspace.

  1. Open Integrations in the builder

    Backend panel, Integrations tab, then Google Drive. To connect it for every project, use Workspace settings, Integrations.

  2. Sign in to Google Drive

    You sign in to Google Drive and approve access. Appbricx keeps the tokens, encrypted, and refreshes them.

    • https://www.googleapis.com/auth/drive

    This uses an OAuth app: the platform's, or your own from the admin panel, and you can bring your own credentials.

  3. Call an action

    From a workflow, by integration id and action name. The call answers with success, output and, when it fails, the reason.

    Workflow
    // .workflow.js (native ctx)
    export async function run(ctx) {
      const res = await ctx.integrations.invoke("google_drive", "list-files", {
        "folderId": "<folder id>"
      });
      if (!res.success) throw new Error(res.error);
      ctx.log.info("Google Drive answered", { output: res.output });
    }

Google Drive and its logo are trademarks of their owner, shown only to identify the service this integration connects to. Their use does not imply endorsement by, or affiliation with, that company.

Connect Google Drive once. Every workflow can use it.