You can export job results from Treasure Data directly to Google Drive, further analyze, share your data in Google Drive, and uncover critical business insights.
View Treasure Boxes for sample workflows to export job results to Google Drive.
- Basic knowledge of Treasure Data, including the TD Toolbelt.
- A Google account (for Google Drive).
- Authorized Treasure Data account access.
You can obtain the Google Drive folder key from the access URL as follows:
If your security policy requires IP whitelisting, you must add Treasure Data's IP addresses to your allowlist to ensure a successful connection.
Please find the complete list of static IP addresses, organized by region, at the following link:
https://api-docs.treasuredata.com/en/overview/ip-addresses-integrations-result-workers/
You must create and configure the export data connection before running your query. As part of the data connection, you provide authentication to access the integration.
Navigate to Integrations Hub > Catalog.
Search and select Google Drive.
The Authentication dialog opens.
Authenticate the connection by selecting an existing OAuth connection or creating a new one.
Select a name for your new Google Drive connection.
Access to Treasure Data Google Drive integration requires OAuth2 authentication. The authentication requires connecting your Treasure Data account to your respective Google account.
If you don't have an existing connection, create a new authentication.
After opening the authentication dialog, select the link under "Sign in with Google" to create a new connection.
Log into your Google Drive account in the popup window and grant access to the Treasure Data app.
You are redirected back to the integration dialog pane. Select Google Sheets and then select the new connection from the dropdown menu.
- Navigate to Data Workbench > Queries.
- Select New Query.
- Run the query to validate the result set.
Navigate to Data Workbench > Queries.
Select an existing query or create a new one**.**
In the query editor, select the Export Results checkbox.
Select your Google Drive connection.
The Export Results dialog panel opens. Edit the following parameters.
The following table describes the parameters you can configure for Google Drive export:
| Parameters | Required? | Description |
|---|---|---|
| File Name | Yes | Name of the uploaded file. |
| Duplication Option | No | One of:
|
| Folder ID | No | Id of parent folder. Drive root folder will be used if empty. |
| Create New Folder | No | Default is false. Checked if creating new folder is required. |
| New Folder Name | Conditionally required | Required when Create New Folder is checked |
| Format | No | One of csv, tsv. Default is csv. |
For csv, tsv formatter and encoder parameters, see CSV Formatter & Encoder
You can create an activation to export segment data or stages.
Review the steps to Creating an Activation in the Product Documentation portal.
SELECT * FROM [table]You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.
Treasure Data's scheduler feature supports periodic query execution to achieve high availability.
When two specifications provide conflicting schedule specifications, the specification requesting to execute more often is followed while the other schedule specification is ignored.
For example, if the cron schedule is '0 0 1 * 1', then the 'day of month' specification and 'day of week' are discordant because the former specification requires it to run every first day of each month at midnight (00:00), while the latter specification requires it to run every Monday at midnight (00:00). The latter specification is followed.
Navigate to Data Workbench > Queries
Create a new query or select an existing query.
Next to Schedule, select None.
In the drop-down, select one of the following schedule options:
Drop-down Value Description Custom cron... Review Custom cron... details. @daily (midnight) Run once a day at midnight (00:00 am) in the specified time zone. @hourly (:00) Run every hour at 00 minutes. None No schedule.
| Cron Value | Description |
|---|---|
0 * * * * | Run once an hour. |
0 0 * * * | Run once a day at midnight. |
0 0 1 * * | Run once a month at midnight on the morning of the first day of the month. |
| "" | Create a job that has no scheduled run time. |
* * * * *
- - - - -
| | | | |
| | | | +----- day of week (0 - 6) (Sunday=0)
| | | +---------- month (1 - 12)
| | +--------------- day of month (1 - 31)
| +-------------------- hour (0 - 23)
+------------------------- min (0 - 59)The following named entries can be used:
- Day of Week: sun, mon, tue, wed, thu, fri, sat.
- Month: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec.
A single space is required between each field. The values for each field can be composed of:
| Field Value | Example | Example Description |
|---|---|---|
| A single value, within the limits displayed above for each field. | ||
A wildcard '*' to indicate no restriction based on the field. | '0 0 1 * *' | Configures the schedule to run at midnight (00:00) on the first day of each month. |
A range '2-5', indicating the range of accepted values for the field. | '0 0 1-10 * *' | Configures the schedule to run at midnight (00:00) on the first 10 days of each month. |
A list of comma-separated values '2,3,4,5', indicating the list of accepted values for the field. | 0 0 1,11,21 * *' | Configures the schedule to run at midnight (00:00) every 1st, 11th, and 21st day of each month. |
A periodicity indicator '*/5' to express how often based on the field's valid range of values a schedule is allowed to run. | '30 */2 1 * *' | Configures the schedule to run on the 1st of every month, every 2 hours starting at 00:30. '0 0 */5 * *' configures the schedule to run at midnight (00:00) every 5 days starting on the 5th of each month. |
A comma-separated list of any of the above except the '*' wildcard is also supported '2,*/5,8-10'. | '0 0 5,*/10,25 * *' | Configures the schedule to run at midnight (00:00) every 5th, 10th, 20th, and 25th day of each month. |
- (Optional) You can delay the start time of a query by enabling the Delay execution.
Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically exported to the specified destination.
Scheduled jobs that continuously fail due to configuration errors may be disabled on the system side after several notifications.
(Optional) You can delay the start time of a query by enabling the Delay execution.
You can also send segment data to the target platform by creating an activation in the Audience Studio.
- Navigate to Audience Studio.
- Select a parent segment.
- Open the target segment, right-mouse click, and then select Create Activation.
- In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
- Customize the activation output in the Output Mapping panel.
- Attribute Columns
- Select Export All Columns to export all columns without making any changes.
- Select + Add Columns to add specific columns for the export. The Output Column Name pre-populates with the same Source column name. You can update the Output Column Name. Continue to select + Add Columnsto add new columns for your activation output.
- String Builder
- + Add string to create strings for export. Select from the following values:
- String: Choose any value; use text to create a custom value.
- Timestamp: The date and time of the export.
- Segment Id: The segment ID number.
- Segment Name: The segment name.
- Audience Id: The parent segment number.
- + Add string to create strings for export. Select from the following values:
- Set a Schedule.
- Select the values to define your schedule and optionally include email notifications.
- Select Create.
If you need to create an activation for a batch journey, review Creating a Batch Journey Activation.
Within Treasure Workflow, you can specify the use of this data connector to export data.
Learn more at Using Workflows to Export Data with the TD Toolbelt.
The TD Toolbelt can trigger exporting the Query Result to Google Drive from the CLI. You need to specify the parameters for the export job using the --result option of the td query command. For more information, refer to Querying and Importing Data to Treasure Data from the Command Line.
td query --database your_database --result configuration queryThe following table identifies the configuration keys with descriptions.
| Config Key | Type | Required | Description |
|---|---|---|---|
| type | string | yes | Export type: google_drive |
| file_name | string | yes | Name of the uploaded file. |
duplicate_option | string | yes | One of allow_duplication, replace, append_datetime |
folder_id | string | No | Id of parent folder. Drive root folder will be used if empty. |
create_new_folder | boolean | No | Default is false. Checked if creating new folder is required. |
new_folder_name | string | No | Required when Create New Folder is checked |
format | string | No | One of csv, tsv. Default is csv. |
skip_invalid_records | boolean | No | If set to true, this will skip invalid records and continue uploading valid ones. If set to false (default), this will terminate the job when an invalid record is encountered. |
td query --database [database name] --query '[sql query]' --type presto \
--result '{"type":"google_drive","file_name":"[file name]","client_id":"[oauth client id]","client_secret":"[oauth client secret]","refresh_token":"[oauth refresh token]","folder_id": "[parent folder id]","create_new_folder": true,"new_folder_name": "[new folder name]"}';To configure csv, tsv format, see https://www.embulk.org/docs/built-in.html#csv-formatter-plugin
To configure encoder, see Encryptio Encoder for Output Plugin