Why Can't I Transfer Voice Notes from Google Drive or iCloud Drive into Dropbox Using Notion Workflow?

This topic was automatically generated from Slack. You can find the original thread here.

Dear Pipedream Community,

Hope everyone is well. So… I must have deleted and reinstalled this workflow (How to Take Perfect Notes with Your Voice Using ChatGPT and Notion - Dropbox version) umpteen times.

The workflow works great when I add new files the RecUp app or save Apple Voice Memos into Dropbox.

However when I try to move from Google Drive or iCloud Drive into the Dropbox folder… these files are not detected and therefore not added to Notion.

I tried to rename them, copy them to create new versions… to see if anything like that works but nothing. They are old voice notes that I want to migrate from an account into a new one (fresh notion, fresh dropbox etc).

One time, it did work but I didn’t realise the credit limit… so I deleted everything and planned to migrate things in chunks over a couple of days but now nothing works… it is this part that really gets me and has me at a loss of how to migrate these across. Is there something in the workflow that recognises files that have already been added to Notion and doesn’t process them again?

Hope that all makes sense!!

Any advice or guidance are gratefully received!

Kind Regards,

Nick

Hi, could you share in short the problem with Pipedream source/action you’re using?

Hi Leo, thank you for your response. I hope this video helps explain things clear…

could you try to upload the file via Dropbox web (instead of using Dropbox sync in your PC)?

success…

Thank you! A simple solution that obviously eluded me!

Glad that it worked! I will create an issue for our Component dev team to check why Dropbox pc sync didn’t work

Thank you and nice to hear that it could help others in the future as well

Hi Nicholas, I’m unable to reproduce the issue. I’ve tested with a new Dropbox trigger on a fresh workflow, and new files that I’ve added to a specific folder are triggered each time. If you try starting with a fresh workflow and new trigger and are still running into issues, please let us know, but for now I’ll close the ticket as I cannot replicate the behavior that you showed in the video.