Dropbox + Transloadit

Build the integration

This Template imports one Dropbox image, resizes it, and returns the output to /processed without creating a sharing link.

1. Create or select a Dropbox app with the file scopes and content access your workflow needs.
2. Connect it as Transloadit Template Credentials named my_dropbox_credentials.
3. Paste the Instructions into a Template and start an Assembly from that Template.

{
  "steps": {
    "imported": {
      "robot": "/dropbox/import",
      "credentials": "my_dropbox_credentials",
      "path": "/incoming/photo.jpg"
    },
    "resized": {
      "robot": "/image/resize",
      "use": "imported",
      "width": 1200,
      "height": 1200,
      "resize_strategy": "fit"
    },
    "exported": {
      "robot": "/dropbox/store",
      "use": "resized",
      "credentials": "my_dropbox_credentials",
      "path": "/processed/${file.url_name}",
      "create_sharing_link": false
    }
  }
}

Authentication

• Connect a Dropbox app through the Transloadit Template Credentials screen and select the narrowest content access and scopes the workflow needs.
• App Folder access is sufficient when the integration only manages its own files; Full Dropbox is necessary to reach existing files elsewhere in the account.
• Dropbox users can revoke an authorization, so production workflows must treat credential failures as recoverable integration errors.

Limitations and operational notes

• Dropbox paths are relative to the app’s selected content root. The same visible path can resolve differently for App Folder and Full Dropbox apps.
• A directory path ending in a slash imports descendants recursively and can produce a large Assembly. Use a file path when only one object is needed.
• create_sharing_link changes the result URL into a Dropbox sharing link. Leave it false for workflows that should not create shared links.