Skip to main content
Question

Google Sheets > Docusign > Google Drive Zap suddenly Erroring at Document Upload Step

  • June 12, 2026
  • 3 replies
  • 27 views

Forum|alt.badge.img

I have two related Zaps for a Docusign template. One creates a new GoogleSheet row for each time the template is used. The other updates the specific GoogleSheet row when the Docusign envelope is completed, and uploads a copy of the completed envelope to a folder on our shared Google Drive. At the “File” step in the Zap, I selected the trigger step “Envelope Completed in Docusign” and the field “Envelope Combined Document (Exists but not shown)”.

I set this up at the end of March, and it has been working perfectly until about a week ago, when I suddenly started getting an error at the File step (which is the step that uploads the completed file to the drive). The error is “Required field “file” (file) is missing”.

I cannot understand why this would suddenly stop working when I have made no changes to it or any of the related programs. I checked to make sure that Zapier and Docusign both have the needed access to the shared Google Drive and they do. I am pulling my hair out. Please help.

3 replies

MohSwellam
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+8
  • Zapier Orchestrator & Solution Partner
  • June 12, 2026

Hi ​@edenschulz ,

 

It does happen sometimes that an app would change its integration. Have you checked if there are any newer versions of the integration ? I would suggest you try and choose a run that errored and check for the file field there


Forum|alt.badge.img
  • Author
  • Beginner
  • June 12, 2026

Thank you - yes I tried replacing the connection for both the GoogleDrive app and the Zapier app integrations, but that didn’t fix the issue.


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • June 23, 2026

Hi there ​@edenschulz 👋 

Like ​@MohSwellam said, there may have been a change to the Docusign integration that altered how the file is being sent to the Zap. If the “Include documents” setting on the trigger is still set to yes then the Zap should be receiving the files but perhaps there was a change made to the integration that affected the naming or ID of the field that contained the file previously. 🤔 

Can you try using one of the recently errored Zap run as the test record for the Zap and then re-select the field that has the file so the Zap uses the same field that’s available when the Zap runs live. You can learn more about how to do that here: Use a previous Zap run as a test record. Once you’ve done that, publish the Zap and try replaying a previously errored Zap run (the entire run not just the errored step so it’s able to use the trigger step’s updated settings) to see if that goes through.

Keep us posted on how that goes!