Read file (storage)
Module · Stable
Pull one file from connected storage onto local disk.
Fetches one file from a connected storage server and returns file_path — a plain local path to the bytes. This is a pure fetch: it does NOT write to memory or the document store. Chain a Document Store step afterward when the file should be ingested (Extract, Ingest to table, Ask AI all read from a stored document); skip it when the file is only needed transiently — emailed onward, or fed straight into Extract / Ask AI without keeping a permanent copy. path is the file path from List files (storage). connection only needs filling in when more than one connection of this storage type exists — leave it blank if there’s just one. One exception to the pure-fetch rule: files above the inline transfer cap read over a headless-Scout bridge are streamed directly into Memory (a permanent document) and return memory_item_id instead of file_path — chaining a Document Store step is unnecessary in that case.
When to use
Section titled “When to use”Use after List files (storage) to pull a specific file’s bytes onto local disk — grab today’s invoices out of a supplier’s SFTP drop folder, read a statement from a WebDAV share, back-fill an S3 prefix. Wire file_path into Document Store when you want the file to persist in Routario’s memory, or straight into Extract / Ask AI / a send step when you don’t.
When not to use
Section titled “When not to use”To only see what files exist use List files (storage). To fetch a URL use HTTP Fetch. Writing back to storage is a separate, deferred capability (Storage write). If you want the file to land in memory (reviewable, searchable, entity-linked), chain a Document Store step after this one — this node itself never writes to memory, with one documented exception: an oversize file read over a headless-Scout bridge is streamed straight into Memory and returns memory_item_id, so no Document Store step is needed for it.
Inputs
Section titled “Inputs”Configured per use: provider, connection, path.
Outputs
Section titled “Outputs”Requires
Section titled “Requires”the storage integration
Auto-generated from the skill registry (load_skills()). Do not edit by hand.