Skip to main content
In a browser automation, agent.download_files navigates a page, finds the download link, and captures the file. Downloaded files are stored in Skyvern’s cloud storage and returned as presigned URLs in the response. If you’re building agents in the Cloud UI instead, use the File Download block. See Block Types and Configuration.

Download a file


Parameters


Response

agent.download_files returns a WorkflowRunResponse. The downloaded files are in the downloaded_files field.

Response fields

Most-used fields: See the WorkflowRunResponse reference for the full field list.

FileInfo fields

Each file in downloaded_files has:

Where files are stored

Files are stored in Skyvern’s managed cloud storage (S3). You access them through the presigned URLs returned in downloaded_files. Files are not saved to your local machine automatically. To save a file locally:

Tips

Set download_suffix to get a predictable filename (e.g., "invoice-q4"invoice-q4.pdf). Without it, files are saved with a system-generated name like download-<timestamp>-<random>.pdf. It does not validate or filter by extension. Raise the overall timeout for large files. download_timeout is a soft hint; timeout is what actually fails the run. Verify with checksums. The checksum field contains a SHA-256 hash. Compare it against expected values to verify file integrity. Login first. Most download portals require authentication. Call agent.login before agent.download_files - the agent reuses the authenticated session.

File operations in agents

If you build agents in the Cloud UI, file operations use dedicated blocks instead of agent.download_files: Files downloaded during an agent run accumulate in a temporary directory and can be passed between blocks using agent parameters. See Agent Blocks Reference for block configuration details.

Full reference