Execution Data node storing multiple values per key

Feature Requests
1

Node: Execution Data (n8n-nodes-base.executionData)

The idea is:

Im passing multiple items into the Execution Data node and it will only store values of the last item. If there are 5 input items to the node, all but the last one are ignored.

Consider that Im storing id (Key) and ID of the record as a value.

My use case:

My workflow processes multiple records per execution and I want to be able to lookup which execution processed any one record by its ID. Today that is not possible, because execution data is only stored for the last record that is passed into the node.

I think it would be beneficial to add this because:

It would be possible to handle the use case above.

Any resources to support this?

Are you willing to work on this?

Yes.

2

I’d treat this as an audit index, not just metadata. For batch workflows, each record id should map back to execution id, item index, node name, and action/result. If only the last item survives, the run can look successful but you still can’t explain which record was processed where.