Google Drive¶
Connects your Salt workspace to a Google Drive account via Carbon integrations. It authorizes access to Drive, discovers eligible files/folders, and prepares them for downstream processing or ingestion steps. The integration type is fixed to Google Drive and all common connector behaviors (inputs/outputs) are inherited from the Carbon data connector base.
Usage¶
Use this node at the start of a data workflow when your source documents live in Google Drive. Typically, you will authenticate the connection (using a Carbon-scoped token), optionally scope which folders/files to include, and pass the resulting handle/output to nodes that fetch, index, or process file contents.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| authentication | True | Not specified | Credentials or token used to authorize access through the Carbon service to your Google Drive data. Typically obtained via a prior authorization step. | |
| selection | False | Not specified | Optional scoping to limit which files or folders from Google Drive are included (e.g., folder IDs, file filters). | {"folderIds": ["12345abcde"], "includeShared": true} |
| sync_options | False | Not specified | Optional synchronization or filtering options (e.g., modified-since time, file types). | {"modifiedAfter": "2024-01-01T00:00:00Z", "mimeTypes": ["application/pdf", "application/vnd.google-apps.document"]} |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| data | Not specified | A handle or reference to the selected Google Drive data within Carbon, to be consumed by downstream nodes that fetch or process file content. | {"provider": "google_drive", "items": [{"id": "1AbCd...", "name": "Report.pdf"}]} |
Important Notes¶
- This node’s integration is fixed to Google Drive through the Carbon connector system.
- Authentication must be scoped correctly to allow access to the target Drive files and any shared drives you intend to include.
- Large folders or many shared drives can increase discovery time; consider filtering by folders or mime types.
- Actual file content retrieval or indexing is typically performed by downstream nodes; this node prepares the source reference.
Troubleshooting¶
- Authorization failed or expired: Regenerate the Carbon-scoped token and re-run.
- No files returned: Verify folder IDs, filters, and that the authorized account has access (including shared drives).
- Partial results: Check rate limits or reduce scope with filters; then re-run to iterate.
- Unexpected file types: Add or adjust mime type filters in the selection or sync options to include the formats you need.