Integrations
Google Drive
Upload a URL-backed file, create a folder, find files by name, or share a file.
What this guide covers
- A Google account through OAuth with access to the intended Drive locations.
- 4 supported workflow actions.
- Drive access and sharing rules are enforced by Google. A connection cannot use files the authorized account cannot access.
- Uploads use a file URL; the action is not a general desktop file picker.
What Google Drive connects
A Google account through OAuth with access to the intended Drive locations.
Upload a URL-backed file, create a folder, find files by name, or share a file.
Prerequisites and permissions
- Google account permission to the target Drive/folder
- Reachable source URL for upload
- Folder, file, or grantee details required by the action
Drive access and sharing rules are enforced by Google. A connection cannot use files the authorized account cannot access.
Connect and configure
- Open the intended Agent Project → Integrations.
- Find Google Drive and select Connect.
- Complete authorization with the correct external identity.
- Confirm the returned connection status is active.
- In the workflow builder, add App Action.
- Select Google Drive, choose one supported action, select the connection, and complete the fields Yanola displays.
- Save and test with controlled data before activation.
Supported actions
| Action ID | What it does |
|---|---|
upload_file | Upload a file from a URL to Drive. |
create_folder | Create a Drive folder. |
find_file | Find files by name. |
share_file | Create a Drive sharing permission. |
Example workflow
Upload a generated report URL to a dated Drive folder and share it with the intended reviewer.
Workflow Trigger → Validate inputs → App Action (Google Drive) → Condition → Notify or End FlowReconnection and token expiration
- Open Integrations when a workflow reports a missing, expired, revoked, or error connection.
- Select Reconnect for Google Drive.
- Authorize the intended identity again.
- Validate access to the exact resource used by the workflow.
- Retest every dependent App Action.
Troubleshooting
| Symptom | What to check |
|---|---|
Connection is expired, revoked, or error | Reconnect from Integrations and complete provider consent. |
Action cannot find a resource | Grant the connected identity access and use the exact provider ID. |
Action input is rejected | Match the action-specific fields and data types shown in the node. |
Test and live behavior differ | Check provider environment, current permissions, external rate limits, and live data. |
Limitations and security
Uploads use a file URL; the action is not a general desktop file picker.
Sharing can expose data externally, so validate grantee and permission before activation.
Never place provider access tokens or secrets in workflow text, logs, screenshots, or AI prompts. Remove unused connections and reconnect only through Yanola.