Skip to main content

I’ve been trying to create a zap where a file uploaded to a Google Drive will be copied to a shared file in OneDrive, but I keep encountering the same API error message no matter how I configure it. 

 

I have re-authenticated OneDrive and r-checked the step configuration. I still get the same error message, after following the trouble-shooting steps. Here is the OneDrive configuration:

 

 

 

And here is the Google Drive step, in case that’s relevant:

 

 

Please help, I’ve been struggling to troubleshoot this problem for weeks. 

Hi @bbehr1 

Help links for using OneDrive in Zaps: https://zapier.com/apps/onedrive/help

It may be related to the selected Shared Folder.

Also, try using the file object returned from Step 1 instead of the Download URL.

e.g. variable is like: File (Exists but not shown)

 


Changing the location from a Shared Folder to a Personal Folder allowed the Zap to go through. What settings should I review with OneDrive to make sure I can access the Shared Folders? 


Hi @bbehr1 👋

I did some digging and found that we’ve got a bug report open for a similar issue where folks are getting authentication errors when uploading files despite the account being connected successfully. These errors seem to be affecting folks that have Zaps connected to a Microsoft free/personal account specifically. And appear to have been caused by a change to Microsoft’s API that is now surfacing these errors for free accounts, but not Business, Group, or Sharepoint accounts.

The error message shown in your screenshot differs from the ones that’s been mentioned on the bug report but if you’ve not got a Business, Group, or Sharepoint Microsoft account connected it’s most likely the same issue.
 
Can you please confirm whether the connected account is on Microsoft’s free/personal plan?
 

If it is I’ll get you added to it right away and will add details of the error you received to the bug report too. Thanks, I look forward to your reply! 🙂


Hi SamB, it’s a business plan. 


Thanks for confirming that @bbehr1. In that case, it’s likely not the same bug. 🤔

Changing the location from a Shared Folder to a Personal Folder allowed the Zap to go through. 

When you changed the selected shared folder to a personal folder did you also select the file object that is returned as "File: (Exists but not shown)”? If so, I’m thinking that could be why it worked as it may be that the "The request is missing a valid API key" error message was be coming directly from Google Drive instead of OneDrive. In which case that would indicate that OneDrive doesn't have permission to access the file.
 
If you have the File (Exists but not shown) field from Google Drive selected in the File field on the OneDrive action, and a Shared Folder selected does that then allow the file to be uploaded successfully? Or does it run into the same error?


Reply