Dropbox OAuth

Professional Dropbox API integration with OAuth 2.0 and automatic token refresh

Overview

This node integrates with Dropbox to manage folders, specifically supporting the deletion of folders. When configured for the "Folder" resource and the "Delete" operation, it deletes a specified folder path from the connected Dropbox account.

Common scenarios where this node is beneficial include:

  • Automating cleanup tasks by deleting obsolete or temporary folders in Dropbox.
  • Managing folder lifecycle in workflows that organize files and folders dynamically.
  • Integrating Dropbox folder deletion into larger automation pipelines, such as removing project folders after completion.

Example: Automatically delete a folder /old-projects/project123 after archiving its contents elsewhere.

Properties

Name Meaning
Path to Delete Path of the file or folder to delete (e.g., /path/to/delete). This is required and specifies which folder will be deleted in Dropbox.

Output

The output JSON object includes:

  • resource: Always "folder" indicating the resource type.
  • operation: Always "delete" indicating the performed operation.
  • deleted_path: The path string of the folder that was deleted.
  • result: The response data from Dropbox API confirming the deletion details.

Example output structure:

{
  "resource": "folder",
  "operation": "delete",
  "deleted_path": "/path/to/delete",
  "result": {
    // Dropbox API response confirming deletion
  }
}

No binary data output is produced by this operation.

Dependencies

  • Requires an OAuth 2.0 authenticated connection to Dropbox with appropriate permissions to delete folders.
  • Uses Dropbox API endpoints, specifically https://api.dropboxapi.com/2/files/delete_v2.
  • Requires configuration of an API authentication token via OAuth credentials in n8n.

Troubleshooting

  • Common issues:

    • Invalid or expired OAuth token: The node attempts to refresh the token automatically but may fail if refresh credentials are invalid.
    • Incorrect folder path: If the specified path does not exist or is incorrect, Dropbox API will return an error.
    • Insufficient permissions: The OAuth token must have permission to delete folders; otherwise, the API call will fail.
  • Error messages:

    • "Dropbox operation failed: <message>": General failure during Dropbox API interaction. Check token validity and folder path correctness.
    • "OAuth token refresh failed: <message>": Indicates failure to refresh the access token. Re-authenticate the Dropbox credentials in n8n.
    • "Unknown folder operation: <operation>": Should not occur if configured correctly; indicates an unsupported operation was requested.

To resolve errors:

  • Verify the folder path exists and is correctly formatted.
  • Ensure the OAuth credentials are valid and have necessary scopes.
  • Reconnect or reauthorize the Dropbox credential if token refresh fails.

Links and References

Discussion