What is the primary function of the Binary Input Loader node?
This node is designed to load binary data, such as files or images, from a specified input field within the workflow item. It converts the reference into usable binary content for downstream processing in your Integrations.
How does the Binary Input Loader differ from standard data nodes?
Standard nodes typically handle JSON text data, whereas the Binary Input Loader specifically focuses on retrieving and preparing binary payloads. This is crucial when dealing with file processing Integrations.
Can I use this node to process files uploaded via an external service?
Absolutely. If a preceding trigger node (like an HTTP Request node) receives a file upload, this node can take the input reference and fully load the binary content for subsequent manipulation or storage.
Does the Binary Input Loader node act as a workflow trigger?
No, this node is an action or utility node, not a trigger. It must be placed after a trigger node or another functional node that provides the necessary input data for the binary loading process.
In what scenario is this node most frequently used within n8n Integrations?
It is frequently used in Integrations where a file reference (like a path or URL) is passed between services, and you need to materialize the actual file content before sending it to another service or storing it using a storage node.