Can't change the owner of a file in Google created through the Service Account

Questions
,
#1

Afternoon. Due to the expiration of my OAuth2 token, I had to connect a Google Service Account on my personal account (@gmail.com).

I am fine with it, but I am concerned that the Service Account is the owner of all the files and folders I have created this way.
I can’t transfer the role of the owner to myself - consent is required.
Is there any way to solve this?

Regards, Aleksandr.

Describe the issue/error/question

What is the error message (if any)?

Please share the workflow

(Select the nodes and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow respectively)

Share the output returned by the last node

Information on your n8n setup

  • **n8n version:0.184.0
  • Database you’re using (default: SQLite):
  • **Running n8n with the execution process [own(default), main]:main
  • **Running n8n via [Docker, npm, n8n.cloud, desktop app]:Docker
    ServiceAcc_owner
    ServiceAcc_owner1230×897 61.6 KB
#2

Hi @asuhan, it seems this behavior is caused by a recent change on Google’s end and is expected:

Following up here, this is the expected behavior as currently Drive does not support the changing of the ownership for items which are owned by gmail.com accounts.

#3

Good day, MutedJam. Thank you. I thought there was some way around it. But there isn’t. It’s a pity that all Google innovations only make life harder for users of their services.

Regards, Aleksandr.

1 Like
#4

There might be a way around it, but unfortunately I am not aware of one :frowning: Might be worth following the aforementioned thread in Google’s bug tracker for that.

I agree with the overall sentiment though, it’s always sad to see a feature disappearing.