Cloud storage and file backup
Google Drive currently provides 2 triggers that can start a workflow and 16 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
New File
Trigger when a new file is uploaded.
New Folder
Trigger when a new folder is created or uploaded.
Create new folder
Create a new empty folder in your Google Drive
Create new file
Create a new text file in your Google Drive from text
Upload file
Upload a file in your Google Drive
Read File Content
Read a selected file from google drive file
Get File Information
Get a file folder for files/sub-folders
List files
List files from a Google Drive folder
Search
Search a Google Drive folder for files/sub-folders
Duplicate File
Duplicate a file from Google Drive. Returns the new file ID.
Save Document as PDF
Save a document as PDF in a Google Drive folder
Update permissions
Update permissions for a file or folder
Delete permissions
Removes a role from an user for a file or folder
Set public access
Set public access for a file or folder
Move File
Moves a file from one folder to another.
Delete file
Delete permanently a file from your Google Drive
Trash file
Move a file to the trash in your Google Drive
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Google Drive event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New File
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Google Drive action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create new folder
Combine Google Drive with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
New File
Finishes with
Create new folder, then preserve the outcome in Coherence
The exact authentication fields depend on Google Drive. The workflow structure stays straightforward:
Authorize the Google Drive account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Google Drive or provide a complementary trigger or action.
Google Drive currently provides 2 triggers that can start a workflow and 16 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Google Drive currently lists 2 triggers and 16 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Google Drive triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
