signed_file_url parameter — CloudCruise fetches the file from that URL at execution time and uploads it to the page. The URL can come from any storage provider (S3, GCS, Azure Blob, etc.) as long as it is publicly retrievable via GET without additional authentication.
The node assumes that the system-level file upload dialog is already opened — add a Click node on the file input trigger before this node.
Parameters
Examples
Basic File Upload
Upload a file using a signed URL:Upload a File From a Data URL
When a page or API hands you the file as adata: URL (for example data:image/jpeg;base64,...), capture it into context and pass it straight to the node:
data: header names the wrong type still uploads as what it really is, and a file_name extension that contradicts the data is corrected (card.png holding JPEG data uploads as card.jpg). Without file_name, the file is named upload.<ext>. The stored copy is not added to the run’s file_urls.
Don’t open a data: URL with a Navigate or Tab Management node to get at the file: Chrome blocks in-place data: navigations, and no later node can run on a data: tab. Pass the data URL to File Upload instead.
File Upload with Custom Name
Upload a file with a specific file name:Notes
- To upload a file downloaded earlier in the same run, tag the File Download node’s
metadataand use{{context.runtime.file_urls[metadata.node="invoice"].signed_file_url}} - When using file uploads, include the file URL in your workflow inputs
- The file must be accessible via a signed URL (pre-authenticated URL), or passed inline as a
data:URL - The file node assumes that the system-level file upload dialog is already opened. Add a click node before the file upload node to trigger this.
- Common file types like PDFs, images, and documents are supported
- For multiple file uploads, use a Loop node that loops over an array of file URLs
- Use
file_namewhen the target website validates or displays the uploaded file name (found under Advanced settings in the workflow editor)

