Hi folks, this is a very old thread that’s easy to overlook as it has already been marked as solved. I’ve recently posted an example workflow storing and reading base64-encoded data in Postgres over here:
To keep track of the file name and mime type I’d simply use a separate columns for easy querying later on. You can read the file name using an expression of {{ $binary.data.fileName }}. The mime type can be read using an expression of {{ $binary.data.mimeType }}. This is assuming your binary property is named data and you are using a recent version of n8n.
Perhaps you want to open a new thread if you run into any trouble with this?