Convert to Text File deleting data

I have a work flow that was working fine a few months ago and now one of the nodes just doesn’t work. I’m using a locally running instance of N8N. I have a node that is receiving JSON data and I’m trying to convert it to a simple text file. The node can see the data just fine but when I run the node, it says it executes successfully, but all the data just disappears. Since there’s no error it’s really hard to tell what’s happening. Any thoughts, ideas or advice would be most appreciated. And again, this was working just a few months ago, I haven’t changed any of the flow and the data source is the same as well.

Before Running the Node:

After running the node:

Hey @kbearman hope all is good, welcome back!

It would be helpful if you could attach your workflow and explain how to reproduce this issue, so that we could take a look.

1 Like

The issue happens anytime I try to execute this node.
I can’t share workflow because I’m running this locally and it doesn’t seem to let me export/share my workflow.

The important piece is that I have a JSON file with a few fields in it. I’m trying to write one of those fields to a text file. And I’m using a different field as the name of the file. But anytime I try to execute this step, the data just disappears, and I get the notification that it “executed successfully”. If there was a debug log or error message it would make life so much easier but I haven’t been able to find one.

Maybe this will help, but this is my data. It’s a JSON with 3 fields.

  • chapter_content
  • chapter_title
  • next_chapter_link

I’m trying to write a text file to the host machine using the chapter_title as the filename and the chapter_content as the contents of the file. I have other flows that are very similar to this, with slightly different data and they work just fine, so I don’t understand what’s breaking here.

Found the problem. It was a permissions issue. The container running n8n didn’t have permission to write to the folder. I’m not sure why exactly that caused this issue but changing the permissions to allow n8n to write to the folder seems to have fixed it.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.