Skip to main content

Hey all I am wondering if anyone else is seeing this behavior lately.

We’ve got a Zap where we send an email with a file attachment to a specific folder in Outlook. Up until recently, the file would always show up in the file section of the Zap, and we could pass it directly into the ChatGPT (OpenAI) step to start a conversation using the content of that file.

Lately, even when attaching the exact same file that used to work, nothing shows up in the file section anymore. Because of that, GPT returns an error saying the file can’t be used or isn’t present, which breaks the automation. Picture 1 was the last time I used Picture 2 is as of today. Same file and same trigger and same everything.

Just curious if others are running into this or if anyone has a workaround. Have you found a way to get Zapier to recognize the Outlook attachments reliably again? Or are you using a different method entirely?

Appreciate any thoughts on this!

 

Picture 1

Picture 2

 

Hi ​@Virgil58 

Try opening a ticket with Zapier Support for them to troubleshoot more: https://zapier.com/app/get-help


Hey ​@Troy Tessalone  

I just send them an email. I figured it was super weird to have that occurring and it's causing some hiccups for us.


I have encountered the same issue when trying to use the MS Outlook trigger with the New Email Matching Search where it finds the correct email but the File object is empty. 

A workaround is to use the MS Exchange w New Email trigger and then apply a filter step to check for the string that would have been included on with the MS Outlook trigger trigger with the New Email Matching Search. 

To test, forward yourself the email w the desired subject and attachments, which should expose the File object for subsequent processing. You can then edit the Subject once Zapier/Exchange picks up the FW which should then preserve the filter params in your Zap. 

The drawback to this workaround is you may have to unzip the file in the email from the Exchange trigger; looks like multiple attachments are in a zip file, which makes sense. 

Would be great if Zapier could address this since this work around requires extra steps and subscriptions to services like Convert API.


Hey there, ​@Virgil58 👋

Looks like our Support team suggested using the "New Attachment" trigger instead which should trigger for each attachment individually, but I couldn’t see any further replies from you on the support ticket, so I’m not sure if that sorted it.

Did you get things resolved by switching to the alternative approach suggested by Derposaurus666 instead, or are you still stuck?

Want to make sure you’re all set here, so please keep us posted on how it went! 🙂


Reply