I totally see what you’re trying to do but this isn’t currently possible. I’m not sure what that would even look like as an option so any additional information you can provide for your use case would help our team out if we ever add more functionality to Dropbox storage.
I think this is a great idea but I’m struggling a bit to see how it could work in a practical use case. You’re correct that Dropbox is a native integration but the integration exists at the app level, meaning all uploads across all tables and fields are uploaded to Dropbox. This applies to existing tables and fields, and newly created tables and fields.
In comparison, the OneDrive pipe is applied at the Data Table, or Record Level (wherever you choose to trigger the pipe) which allows for significantly more granular control over what fields are used as parameters, and ultimately what folders are created and where uploads for specific fields are saved.
I wonder if a Dropbox pipe would be the answer here.