Google Drive
You can create a Google Drive Destination Connector to write CSV files (by default) or JSONL files to a Google Drive folder using your Google account. We do not currently support Shared Drives.
To set up this Destination Connector, your Google account will need access to the Google folder you are connecting to.
Supported file formats: We only write to CSV or JSONL files. We cannot write to a Google Sheet using a Google Drive Connector. To write to a Google Sheet, please set up a Google Sheets Connector.
If you have multi-factor authentication enabled for your Google account, you may need to recreate the Destination Connector when the authentication expires. Re-authentication for existing connections is coming soon.
Required information:
- 1.Google Drive Folder URL
- 2.Google Account Username and Password
Step 1: After selecting + New Connector, under the System prompt, click Google Drive.
Step 2: Provide a Connector Name.
Step 3: Select Destination Connector.
Step 4: Provide the Folder URL.
Use the schema designer to build the output schema for this Destination Connector.
Parameter | Description |
Field Name | Provide a field name for the output fields. These names will be used as the column headers or field names in the output file you are writing to. |
Type | Define the type of each field. The field types will be used to enforce rules when you send data to this Connector. |
Nullable | Check this box if the field is nullable. If the field is not nullable, you will be required to provide values for this field when sending data to this Connector. |
Delete | Deletes the field. |
Add Field | Adds another field to the schema. |
1. Click Add Field for each additional field required in the schema.
2. Select Create Schema once you have built the schema.
Output File Format
By default, this Destination Connector writes CSV files, and each Osmos Pipeline run produces a new file. If preferred, you can choose to change the output to JSONL files instead of a CSV files.
We support the designation of file prefixes in order to more easily manage the output of this connector. The contents of this field will be written into the filename of the data this Connector writes. If a prefix is specified, a UUID will be appended to it to prevent filename conflicts.
By default, we do not set a limit on the number of records to be written to a single destination file by a single job (i.e. a single run of a Pipeline or Uploader). If this box is checked, the data written to the destination will be "chunked" into separate files which contain at-most the number of records designated here. These "chunked" files will be suffixed with it's position in the sequence i.e. filename_part_1.csv, filename_part_2.csv, etc.
We support the use of Validation Webhooks to prevent bad data from being written to your systems, adding another layer of protection to the built-in validations that Osmos provides. The Webhook URL can be posted here.
Enter the name of the destination column where you'd like to store the entire raw source record data. The raw source record data will be stored as a JSON string in the provided destination column.
Organizing File Structure
A user can chunk files and output to a different naming structure based on job_id. Osmos leverages a case-sensitive magic string {jobId} in the file prefix and the file output names for these file based Destination Connectors. To set a file prefix, go to the Destination Connector > Show Advanced Options > populate prefix information in the File Prefix Format String field.
We support the designation of file prefixes in order to more easily manage the output of this connector. To set a file prefix, go to the Destination Connector > Show Advanced Options > populate prefix information in the File Prefix Format String field. The contents of this field will be written into the filename of the data this Connector writes. A UUID will be appended to the filename to it to prevent writing conflicts. Osmos leverages two types of magic string identifiers in order to include additional information in your file prefix.
Job_Id: You can include an identifier that corresponds each individual Job (a run of an Osmos Uploader or Pipeline) by including {jobId} in your prefix format string. See examples 3 & 4
DateTime: You can include datetime values in your file output using String from time (strftime) format specifiers. The time values created here correspond to Osmos internal system time at the moment the job was started. See example 4
Output Scenarios:
- 1.No file prefix Output: <user base path>/chunk-<chunk num>-<UUID>.<file extension>
- 2.File includes description in the prefix Sample prefix: my_osmos_output_ Output: <user base path>/my_osmos_output_chunk-<chunk num>-<UUID>.<file extension>
- 3.File includes description and job_id in the prefix Sample prefix: my_osmos_output_{jobId}_ Output: <user base path>/my_osmos_output_<ACTUAL JOB_ID HERE>_chunk-<chunk num>-<UUID>.<file extension>
- 4.File includes datetime specifiers and job_id in the prefixSample prefix: {jobId}_%F_%T_ Output: <user base path>/<ACTUAL JOB_ID HERE>_<YYYY-MM-DD>_<HH:mm:ss>_chunk-<chunk num>-<UUID>.<file extension>
Last modified 1mo ago