A Full Set of Connections
Integrations enable the transfer of data across your technology stack. You can move data into and out of the Treasure Data Platform. You can also move data between databases within the platform (see Treasure Data Data Exchange).
To facilitate this, Treasure Data provides a user interface for most integrations.
You can see a full set of integrations from the console, Source Catalog page: https://console.treasuredata.com/app/connections/data-sources.
Treasure Data also offers integrations that do not have a UI implementation, for example for Bulk Import. When you don't use the UI to create a data connector, you can configure a data connection by creating a .yml file. The documentation for each specific data connection provides steps for configuring a data connection both using the UI and, alternatively, creating a .yml file.
Importing data into Treasure Data
When you configure a data connection, you provide authentication to access the data source. You can see a list of all your configured and saved data connections from the console, "My Connections" page: https://console.treasuredata.com/app/connections/my-connections.
After you create and configure the data connection, you can create input transfers that specify the specific source, the schedule for import, and also specify where in Treasure Data to put the incoming data. It might help you to think of Input Transfers as a specific instance of a data connection.
You can see your input transfers from the console, Input Transfers page: https://console.treasuredata.com/app/connections/data-transfers
Exporting data out of Treasure Data
You might see the term Results Output or Export Results used in association with export activities. Export Results allow you to send the results of a query to a destination. Data Connections are used to export query results out from Treasure Data to the target destination. As with import, you must create and configure the data connection to be used during export, prior to running your query.