Governance
List a human step's input files
List a human step’s input files. Requires a Personal key and permission approvals:read.
GET
List a human step's input files
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
Lists the files a human workflow step was handed, metadata only: each file’s input key,fileId,
name, MIME type and size. A file whose row is gone is listed with available: false rather than
dropped, so a caller still knows an attachment was expected. Read a file’s content with
getHumanTaskInputFileUrl.
Who may open a step
The Personal key’s owner may open a step that asks them (they are among the step’s notified people), or any step when they holdapprovals:approve at the platform through a key whose scopes
reach it — the same two doors the Console’s download links use. A step the owner may not open, a
missing step and a malformed id all answer the same 404. A platform key or an External App gets
403 with error.personRequired: true.
By humanTaskId, the task is read first, exactly as
getHumanTask reads it, and then its step is
opened by the same two doors. A task the owner may not read, and a task that is not a workflow
step’s, answer the same 404, so the answer never says whether a task exists. A step’s notified
people get its node run id from My Work; humanTaskId is for a caller who has only the task: one
who reached it through getHumanTask or attention, whose step is closed or past My Work’s cap, and
who gets no reassignRef unless they could take the task over.
getHumanTaskInputFileUrl names
the step the same two ways.
Parameters
Example
forge_list_human_task_input_files returns the same data and meta.Authorizations
A Personal key (fmcp_…), bound to the person who created it, or an interactive MCP sign-in that resolves to one. Pass as Authorization: Bearer <key>. It acts for that person, under their role grants narrowed by its scopes; an operation that acts for a person admits only this kind.
Query Parameters
Response
The step's input files

