Thanks @MarinaH! It does all work with the Action essentially hitting the API for a list of the items every time it gets run but that’s obviously a lot of redundancy. That all said, our integration is still private and being developed...and I think we’ve decided that this level of item specificity isn’t required at this time.
In terms of the other information (just for anybody else who ever reads this thread later on) I did give the Lookup table a shot - if it could accept a set of line items for both the key and value and create a pair for each - but as you noted it would need to be more of a manual process there.
I did think that you could also set this up with Tables as well if necessary and use that as a cache of information, either by getting a list of the items at the beginning of the Zap via a general search action, or by having a separate Zap that is triggered by a webhook fired by the API when changes to the list of items occurs...which then adds that info to the table.
Anyhow, thanks for the information and confirmation - all well thought out and makes sense!