Integrations
Upload to Dropbox Block
Upload to Dropbox sends an existing file variable or artifact to a Dropbox path.
At a glance
Best for
Dropbox delivery
Input
File variable
Requires
Dropbox connection
Error handle
Yes
What it does
Upload to Dropbox moves generated files from Scrapeer into Dropbox.
Use it after a Block has already produced a file artifact.
Use it when
- Upload generated reports to Dropbox.
- Store scheduled run exports in a Dropbox folder.
- Save screenshots or PDFs for later review.
Do not use it when
- The source value is not a file.
- No Dropbox connection is configured.
- The destination path is not writable.
Settings
Upload to Dropbox needs a connection, source file variable, path/name, overwrite behavior, and output variable.
Connection
Required: Yes- Variables
- No
- Description
- Dropbox connection.
Source variable
Required: Yes- Variables
- Variable name
- Description
- File variable or artifact to upload.
Path and filename
Required: Yes- Variables
- Yes
- Description
- Dropbox destination path.
Output variable
Required: No- Variables
- Variable name
- Description
- Stores uploaded file metadata.
Outputs
Upload to Dropbox returns provider file metadata.
{{outputVariableName}}objectUploaded file metadata returned by Dropbox.
Example Flow
Use Upload to Dropbox after creating a file output.
- Create a file artifact.
- Upload it to Dropbox.
- Use the returned metadata if needed.
Errors and fixes
Start with symptoms visible in the editor or Inspector, then check the earliest Block that produced the wrong page state, variable, or output.
The source file is missing.
- Check
- Check upstream file output variable names.
- Fix
- Pass a file variable from Save File, Create Spreadsheet, Create PDF, or Screenshot.
The upload is denied.
- Check
- Check Dropbox connection permissions and path.
- Fix
- Use a writable path or reconnect Dropbox.
Local and cloud runs
Cloud uploads expect a file artifact. Local runs can use compatible file variables created upstream.