Skip to main content Skip to complementary content

tDropboxPut Standard properties

These properties are used to configure tDropboxPut running in the Standard Job framework.

The Standard tDropboxPut component belongs to the Cloud family.

The component in this framework is available in all Talend products.

Basic settings

Use Existing Connection

Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined.

Access Token

Enter the access token required by the Dropbox account you need to connect to. This access token allows Talend Studio to make Dropbox API calls for that Dropbox account.

Note that a Dropbox App should have been created under that account before generating the access token. For further information about a Dropbox access token, see

Use HTTP Proxy

If you are using a proxy, select this check box and enter the host and port information of that proxy in the corresponding fields that are displayed.

Path (File Only)

Enter the path pointing to the file you need to write contents in. This file will be created on the fly if it does not exist.

Note that the path string should start with a slash (/). It is the root folder of the Dropbox App for which you are using the current access token.

Upload Mode

Select upload mode to be used:

  • Rename if Existing: the uploaded file is automatically renamed. For example, a file named test.txt might be renamed to test (1).txt.

  • Replace if Existing: the uploaded file replaces the existing one.

  • Update specified Revision: the file you are uploading is used to update a specific revision of that file. If the revision you specify is the latest revision, then the existing file on Dropbox is replaced; if it is an older revision, the file you are uploading is renamed to indicate that a conflict is encountered; if the revision does not exist, an error is returned.

Upload Incoming content as File

Select this radio button to read data directly from the input flow of the preceding component and write the data into the file specified in the Path field.

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

Note that the schema of this component is read-only with a single column named content and it receives data from the content column of its input schema only. This means that you must use a content column in the input data flow to carry the data to be uploaded. This type of column is typically provided by the tFileInputRaw component. For further information, see tFileInputRaw.

The Schema field is not available when you have selected the Expose as OutputStream or the Upload local file radio button.

Upload local file

Select this radio button to upload a locally stored file to Dropbox. In the File field that is displayed, you need to enter the path or browse to this file.

Expose as OutputStream

Select this check box to expose the output stream of this component as a variable named OUTPUTSTREAM so that the other components can reuse this variable to write the contents to be uploaded into the exposed output stream.

For example, you can use the Use output stream feature of the tFileOutputDelimited component to feed a given tDropboxPut's exposed output stream. For further information, see tFileOutputDelimited.

Advanced settings

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at the Job level as well as at each component level.

Global Variables


The error message generated by the component when an error occurs. This is an After variable and it returns a string.


Usage rule

This component is used either standalone in a subJob to directly upload a local file to Dropbox or as an end component of a Job flow to upload given data being handled in this flow.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!