Skip to main content

Connect

Establishes a connection to Dropbox using an access token for use in subsequent Dropbox operations.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Options​

  • Dropbox Token - The Dropbox API access token credential used to authenticate with the Dropbox API.

Output​

  • Client ID - A unique identifier for the Dropbox connection that must be used in subsequent Dropbox operations.

How It Works​

The Connect node is the first step in any Dropbox automation flow. It securely stores your Dropbox access token and returns a client ID that is used by all other Dropbox nodes in the flow.

When executed, the node:

  1. Retrieves the access token from the provided credentials
  2. Stores the token in a thread-safe token manager
  3. Returns a unique client ID that references the stored token
  4. This client ID is then used by other Dropbox nodes to authenticate API requests

Requirements​

  • A valid Dropbox account
  • A Dropbox access token (can be generated in your Dropbox App Console)
  • The access token must be stored as a credential in Robomotion

Generating a Dropbox Access Token​

To get a Dropbox access token:

  1. Go to the Dropbox App Console
  2. Create a new app or select an existing one
  3. In the app settings, generate an access token
  4. Copy the token and store it as a credential in Robomotion

Error Handling​

The node will return specific errors in the following cases:

  • Invalid or missing Dropbox token credential
  • Empty token value in the credential

Usage Notes​

  • The Connect node should be executed before any other Dropbox operations
  • The returned Client ID must be passed to subsequent Dropbox nodes
  • Each Connect node creates a new token entry that should be cleaned up with a Disconnect node
  • For security, always use the Disconnect node to remove the stored token when it's no longer needed
  • The token is stored in memory only and is automatically removed when the flow stops

Best Practices​

  • Store your Dropbox access token as a credential rather than hardcoding it
  • Use a single Connect node at the beginning of your flow
  • Always pair Connect with Disconnect nodes to properly clean up resources
  • Handle errors appropriately to prevent credential leaks
  • Use scoped access tokens with minimal required permissions for better security

Example Flow​

A typical Dropbox automation flow starts with the Connect node:

Connect (returns client_id)
  ↓
UploadFile (uses client_id)
  ↓
ListFiles (uses client_id)
  ↓
Disconnect (uses client_id)