Skip to main content
The File Download node waits for a file download to complete and stores it with metadata. This node does not trigger the download itself—the download must be initiated by a previous action (e.g., a Click node on a download button). The exception is when trigger_print is set, which triggers the browser’s print dialog for PDF generation. The node polls for a download to complete before timing out. By default, the timeout is 60 seconds, but this can be configured using the timeout_seconds parameter.

Parameters

Examples

Capture a Download

First trigger the download with a Click node, then capture it:
Then capture the file. You can include workflow context in the metadata:

Use the File Later in the Run

Every File Download node adds the files it captured to context.runtime.file_urls, so later nodes can use them, for example to upload a file to another site with a File Upload node. Tag the download in metadata and select it by that tag:
context.runtime.file_urls holds every file downloaded so far in the run, with the same fields as the entries in file_urls: signed_file_url, file_name, timestamp, signed_file_url_expires and metadata. It stays out of the run’s data output.
  • Select by a metadata tag, not by position: an earlier or failed download shifts [0] and [-1].
  • If one node captured several files, add a filter such as [metadata.node="invoice" and file_name="statement.csv"], or loop over {{[context.runtime.file_urls[metadata.node="invoice"]]}}. The outer brackets keep the result a list when only one file matches. A selector that matches several files fails the File Upload node.
  • Inside a loop, add the loop index to the tag, e.g. "metadata": { "node": "invoice", "i": "{{context.runtime.INDEX_1}}" }, and filter on both.
  • file_urls is reserved and cannot be used as a loop variable name.

Expect Print Dialog

With expect_print_dialog, the agent waits for the browser’s print dialog to open and only then sends the OS-level key sequences that save the PDF. The wait is bounded by the node’s timeout_seconds. If the dialog does not open in time, no keystrokes are sent and the run fails with DOWNLOAD-E0002.
Enable this when the previous step (e.g. a Click node) opens a native print dialog. The typical pattern is:
  1. Click node — clicks a “Print” button that opens the browser’s native print dialog
  2. File Download node with expect_print_dialog: true — waits for the print dialog, then saves the printed PDF

Notes

  • This node waits for a download. Use a Click node before it to trigger the actual download
  • The node captures every download that has finished by the time it first sees one; each becomes its own entry in file_urls. A download that finishes later is left for the next File Download node, so when one click starts several downloads, add a short Delay before this node
  • Downloaded files are stored and accessible in the workflow results
  • Downloaded files are added to the file_urls array in the response payload (available in both the API response and webhook events)
  • Each downloaded file triggers a file.uploaded webhook event with the signed file URL and metadata
  • The trigger_print option triggers the browser print dialog for PDF generation
  • Set continue_on_failed_download: true for optional downloads that shouldn’t fail the workflow
  • continue_on_failed_download does not cover print failures. With trigger_print or expect_print_dialog, if the print dialog does not open or the PDF cannot be saved while the dialog is open, the run fails with DOWNLOAD-E0002, because an open print dialog blocks the page. An upload failure after the PDF is saved is handled like any other failed download
  • A very long page, such as a report with thousands of rows, can crash the browser tab while it prints, because Chrome limits the memory of each tab. The run then fails with DOWNLOAD-E0003. Print fewer rows per job: narrow the page’s filters (for example, split the date range into smaller parts) and print each part
  • Downloaded files are limited to 150 MB. Larger files fail the node with an upload error
  • Supported file types: PDF, images (PNG, JPEG, GIF, WebP, TIFF), text, CSV, JSON, XML, Excel (XLS, XLSX), Word (DOCX), and ZIP
  • Signed file URLs expire based on your workspace settings (default: 7 days, configurable from 1 hour to 7 days). Configure this in workspace settings
  • The node times out after the configured timeout_seconds (default: 60 seconds) if no download is detected