Legacy Slack to Google Docs upload issue: Files invisible post-update

Hi ​@zenoffice! 👋

Sorry to hear that your Zap is no longer working. I’ve not seen any similar reports of this (yet!) but my initial thoughts are that it could be that one of a fields that was previously available with that Slack trigger has been renamed or changed in some way. If that’s the case then loading in a new test record from Slack and re-selecting the fields could help to get things working again.

Can you give that a try and let us know how it goes?

If it doesn’t work can you share some screenshots showing the current setup of the Slack trigger and Google Docs action? As I’d like to see what fields and settings have currently been selected so we can get a better idea of what might be causing the trouble here. Also, if you could also share a screenshot showing how it the files appeared within the Google Doc previously so we can see what the Zap should be creating instead of a blank document that would be super helpful too. Please make sure to blur or remove all personal information (names, emails, addresses etc.) from screenshots before sharing - you can use a tool like Zappy for that.

Look forward to hearing from you! 

Hi ​@zenoffice,
 
We just wanted to see how everything is going with your Zap. Did Sam's recommendation get the job done? Feel free to reach out if you need further assistance with your Zap. We're glad to address any concerns and assist you.
 
We're looking forward to your response.

Thank you for replying.

This picture is a screenshot example. Not only txt files but other file types this problem is happening.

The problem ocurres when I choose “Files 0 File”.

Follwing pictures are the setting of google document action.

For reference, when I set the slack action as the legacy version with the exact same settings , a google document is created that reflects the file with its contents.

I have the same issue and it is breaking many of my automations. Please help!

Hi ​@zenoffice and ​@Alinardo! 👋

​@zenoffice - thanks for sharing those helpful screenshots. I’ve replicated your set up to do some testing in one of my own Zaps and you’re right, uploaded files are indeed being created as empty documents! I even tried with a Google Drive action and it created a blank document too.  

I then tried uploading it to Dropbox and it didn’t create a blank file, but it still didn’t upload what I was expecting. It uploaded the HTML from the web page that’s accessible from the URL in the Files 0 Permalink field. So it definitely seems like there’s an issue with how files are being sent over from Slack! I’d recommend that you both contact our Support team here to get this investigated further. They’ll be able to open up a bug report so that our engineers can work on getting this resolved.

Keen to ensure this gets sorted so please keep us updated on how you both get on with them. If they’re able to come up with a workaround we’d love to have it shared here in the Community! 🙏

Thanks you for replying and testing.

As you told me, I will contact the Supprot team and share in this community !

Thanks so much for doing that ​@zenoffice 🤗 Look forward to hearing how you get on! 

I am having the same issue. All of my Zaps with Slack are broken. I fixed the issue by using the legacy version of slack and everything went back to normal. However slack keeps automatically changing to the new version and then they all break again. ZAPIER please fix this.

We apologize ​@Benwillski, as of now we don’t have any update yet in regards with the issue, for the meantime you can use the legacy version of your Slack to continue with your Zap. We strongly suggest to contact our Zapier Support to log every details on the error that you are getting.

Now we are inquiring about this matter but have not received a clear answer.

I’ll share this in the community if we received good answer.

Thank you.

Thanks for letting us know ​@zenoffice. That would be great—would love to know how things progress with the Support team on this. If you have any further questions or if there’s anything else we can assist with in the meantime, don’t hesitate to reach out! 🙂

hi, SamB

we have no good news yet.

We have asked about this issue, but it appears that Zapier support has not yet asked their engineers to investigate.

We need to make them aware that there are others who have the same problem besides us.

Can you help us?