Scrapeer
Integrations

Upload to S3 Block

Upload to S3 sends an existing file variable or artifact to an S3 object key.

At a glance

Best for
S3 object storage
Input
File variable
Requires
S3 connection
Error handle
Yes

What it does

Upload to S3 moves generated Scrapeer files into S3-compatible object storage.

Use object keys to control the destination path and filename.

Use it when

  • Store scheduled run artifacts in S3.
  • Upload CSV or JSON exports for downstream processing.
  • Archive screenshots, PDFs, or generated files.

Do not use it when

  • The source is not a file variable.
  • No S3 connection is configured.
  • You need a human-facing spreadsheet first; use Create Spreadsheet before upload.

Settings

Upload to S3 needs a connection, source file variable, bucket/key settings, overwrite behavior, and output variable.

Connection

Required: Yes
Variables
No
Description
S3 connection.

Source variable

Required: Yes
Variables
Variable name
Description
File variable or artifact to upload.

Object key

Required: Yes
Variables
Yes
Description
Destination object path and filename.

Output variable

Required: No
Variables
Variable name
Description
Stores uploaded object metadata.

Outputs

Upload to S3 returns object metadata.

{{outputVariableName}}object

Uploaded object key, bucket/provider metadata, and URL fields when available.

Example Flow

Use Upload to S3 after creating a file artifact.

  1. Create a file artifact.
  2. Upload it to S3.
  3. Use the returned object 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 upload cannot find the file.

Check
Check source variable name and upstream file Block output.
Fix
Use the file variable created by Save File, Create Spreadsheet, Create PDF, or Screenshot.

The upload is denied.

Check
Check S3 connection, bucket, and object key permissions.
Fix
Use credentials with write access to the target bucket/key.

Local and cloud runs

Cloud uploads expect a file artifact. Local runs can use compatible file variables created upstream.

Blocks

Understand how Blocks connect and pass state through a Flow.

Runs and outputs

Inspect Block output, errors, and variables after a run.