Answer
Add an IFS API task that reads the relevant entity set first, passing its key parameter (like the record's own number/ID) — once that read task exists in the workflow, the custom attribute becomes available to reference from later steps; a custom attribute being visible on the page and in the API docs doesn't automatically make it addressable in the workflow without first reading the record it belongs to.