Google Drive “Update Content in a File” no longer preserving newline characters

Hi,

I have a long-established Pabbly Connect workflow which has been running successfully for over a year without any manual changes. It processes CSV data in a JavaScript step and then uses:

Google Drive → Update Content in a File

to update a Google Sheets file.

The workflow was working correctly up to 19 August 2026, but since then newline characters in the file content appear to be handled differently. Instead of creating separate CSV rows, the data is being written horizontally across a single spreadsheet row.

I have now reproduced the problem in a duplicated workflow using a completely separate test Google Sheet, so the issue is not dependent on my original data, JavaScript processing or production spreadsheet.

As a simple test, I entered the following directly into the File Content field of the Google Drive “Update Content in a File” action:

A,B,C
1,2,3
4,5,6

Rather than creating three spreadsheet rows, the resulting file contains effectively one row, with the newline characters being treated as literal \n content rather than CSV record separators.

I have also compared historical task data. On 19 August, the same existing workflow successfully passed multiline CSV content through this Google Drive action and produced the correct spreadsheet structure. The workflow has not been manually changed since then.

The JavaScript step immediately before the Google Drive action is still outputting correctly separated multiline CSV. For example, Chunk 1 contains a header followed by 300 separate records, and the subsequent chunks are also correctly newline-separated. The corruption therefore appears to occur when the content is handled by the Google Drive → Update Content in a File action.

The target file is a native Google spreadsheet (application/vnd.google-apps.spreadsheet), and the action is using the Google Drive upload endpoint.

Could you please investigate whether there has been a recent change or regression in the Google Drive “Update Content in a File” action, particularly in the handling/escaping of newline characters (\n) in file content?

I can provide:

• successful task history from 19 August;
• failing task history from 31 August;
• the original JavaScript output showing correct multiline data;
• the resulting malformed spreadsheet;
• screenshots of the Google Drive action configuration;
• the isolated A,B,C test described above.

This is affecting a production workflow, so I'd appreciate it if this could be escalated to the technical/integration team if necessary.

Many thanks.