trigger_print is set, which triggers the browser’s print dialog for PDF generation.
The node polls for up to 60 seconds waiting for a download to complete before timing out.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
metadata | object | Yes | Metadata to attach to the downloaded file for identification in results |
trigger_print | boolean | No | If true, trigger browser print dialog for PDF generation instead of waiting for a download |
continue_on_failed_download | boolean | No | If true, continue workflow even if no download is detected within the timeout |
Examples
Capture a Download
First trigger the download with a Click node, then capture it:Notes
- This node waits for a download. Use a Click node before it to trigger the actual download
- Only one download can be captured per File Download node. If multiple downloads are triggered, only the last one is captured
- To capture multiple files, use separate Click → File Download node pairs for each file
- Downloaded files are stored and accessible in the workflow results
- Downloaded files are added to the
file_urlsarray in the response payload (available in both the API response and webhook events) - Each downloaded file triggers a
file.uploadedwebhook event with the signed file URL and metadata - The
trigger_printoption triggers the browser print dialog for PDF generation - Set
continue_on_failed_download: truefor optional downloads that shouldn’t fail the workflow - The node times out after 60 seconds if no download is detected

