@Hae, Well if you are going to use ExecuteSQL to execute the INSERT Statement based on the content of the file, from my point of view you should first extract the value of your content as an Attribute to your FlowFile. To do that, you add an ExtractText Processor, where you define a new property named "what_you_want_to_have_it_called" and assign it the value ".*". This will extract the content of your flow file and store it in the attribute you defined as a property. NOTE: if you are going to have lots of information stored in the content of the flowfile, you will encounter so many issues doing the above mentioned. Take into consideration that this is going to work properly if working with small flowfiles, exactly like you described in your post 🙂 Next, using ExecuteSQL, you are going to execute the insert like: "insert into table value(${what_you_want_to_have_it_called}). Another option which might not involve all these steps would be to use and PutDatabaseRecord Processor, in which you can define directly the action you are trying to perform and it will handle everything for you. NOTE: this is going to work ok for larger flowfiles, as you no longer need to extract the content as attributes and NiFi will handle everything on its own. The only single downside is that you will have to configure an Record Reader. ... View more