Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hello,

I'm currently building a Zap that sends a PDF file via Gmail. I'm following the instructions from this Zapier help article:
Send files in Zaps

Context:

  • The PDF file I'm trying to send is stored in a Shared Google Drive.

  • I use the Google Drive → Find File action to locate the file.

  • The testing the Google Drive → Find File action returns a successful result and shows various outputs. 

  • In the next step (Gmail → Send Email), I map that file field into the Attachment field.

  • The Attachment field now shows “6.File: (exists but now shown))” 

  • This setup previously worked — the PDF was successfully attached and delivered via Gmail. The successful flows ran a few day ago, just today it is throwing errors. 

Issue: Now, running the same flow gives me this error in the Gmail step:
"Cannot read properties of undefined (reading 'log')"

If I remove the attachments from the Gmail step, the email sends successfully. But re-adding the same mapped file causes the error to return. I’ve tried re-testing the Find File step and remapping the attachment field, but the issue persists.

Questions:

  • Has anyone encountered this error when attaching files from Google Drive in Gmail Zaps?

  • Could this be related to shared drive access restrictions or a recent connector update?

Appreciate any insight or recommendations. I’m happy to provide more details or screenshots if needed. Thank you.

Hi ​@KaratIT 

For us to have more info, post these screenshots:

  • the encountered Zap Run step error
  • DATA IN for the Gmail step from the Zap Run
  • how your Gmail Zap step is configured in EDIT mode with the field mappings visible

Hi ​@Troy Tessalone , 

Here is more information I can provide: 

I notice the Zap Run Step Error in the history is different from what I posted, it shows this:
 

Data in for this Zap Run: 
 

 

Gmail Zap step in edit mode: 

When I retest the card only and don’t run the whole workflow I get this error instead:
 

 

​@KaratIT 

Try replaying the entire Zap Run to see if it was a temp issue.

https://help.zapier.com/hc/en-us/articles/8496241726989-Replay-Zap-runs#h_01H9KDDTA18A8Y0YXD4B8RP4JC

 

Check if you need to adjust the file share preferences for the GDrive File.

 

I have the same issue! Before it worked, but now it doesn’t. It looks like something on Zapier side - in the gmail zapier step configs. 

​@afanasenko and ​@KaratIT 

Try opening a ticket with Zapier Support: https://zapier.com/app/get-help

Hey everyone,

Just wanted to share an update and resolution I found regarding an issue I had with Gmail attachments not sending properly in a Zap.

To troubleshoot, I created a brand-new Zap with only two steps:

  1. Google Drive – Find a File

  2. Gmail – Send Email

I kept it simple to rule out interference from other steps. After testing the "Find a File" step, it correctly located the PDF in my Google Drive. I then mapped that file output to the attachment field in the Gmail step. When I tested the Zap, the email sent successfully with the PDF attached—no issues at all.

I then went back to the original Zap where I initially had problems and tested the Gmail step again. This time, it worked just fine and included the attachment. Looks like the issue might have resolved itself—possibly something temporary on Zapier’s end.

I'll keep an eye on it and follow up if anything changes, but for now everything seems to be working as expected. Hope this helps anyone else running into similar issues!

Thanks again to everyone who chimed in earlier! 

Really appreciate you sharing that update here, ​@KaratIT. So pleased it’s working now! 🎉 

Fingers crossed it stays resolved, but please do keep an eye on things and let us know if the issue resurfaces at all. 

In the meantime, happy Zapping! ⚡️

Terms & Conditions