Memory fetch file
Module · Stable
Resolve a memory item’s stored file to a local path.
Given a memory_item_id, returns file_path — a local path to the item’s stored file, the same output shape Read file (storage) returns. Unlike Read file (storage) this never fetches or writes anything new; the file is already permanently stored in memory, this just resolves where. found is false when the item doesn’t exist or has no file on disk (e.g. a plain text note). parent_doc_id is set when the item is an email attachment — Get memory item never resolves an attachment’s own id (only the parent email body becomes a readable memory item), so call Get memory item on parent_doc_id instead to read the surrounding email’s text and mentioned entities.
When to use
Section titled “When to use”Whenever a step or agent holds a memory_item_id (from the ‘Memory item annotated’ trigger, List memory items, or Get memory item) and needs the underlying file’s bytes — to re-file it elsewhere (Storage write), attach it to an outgoing message, or run it through Extract. For an email attachment specifically, call this FIRST (before Get memory item, which won’t find the attachment itself) and use the returned parent_doc_id to read the email’s own content for context.
When not to use
Section titled “When not to use”To read a memory item’s extracted text and mentioned entities, use Get memory item instead — most flows only need that, not the raw file. To fetch a file from an external connected storage server, use Read file (storage).
Inputs
Section titled “Inputs”Configured per use: memory_item_id.
Outputs
Section titled “Outputs”Auto-generated from the skill registry (load_skills()). Do not edit by hand.