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.

I have a simple Zap where I’d like when a File is uploaded to an opportunity in Salesforce, that file then also gets uploaded to a Google drive. In my Zap however, I don’t see the option to reference the file URL or otherwise tell Google drive which file to upload. Am I missing something? If that is not supported in this Zap action then the action seems kind of pointless.

 

Alternatively, I can trigger on when a new record is created for “Content Document”, but if I do that, I cannot get the parent info (all I want is the opportunity name).

 

Any guidance is appreciated, thank you.

Hey ​@zap-ss-ad,

Can you post the Data Out from Salesforce trigger to see in which format file is there? If the trigger is not giving you the details to pass the file to google drive. You can try to use Get Record Attachments to get the files-

 

Hope it helps!

Hi ​@zap-ss-ad 

Help links for using files in Zaps: https://help.zapier.com/hc/en-us/articles/8496288813453

I am not seeing the “File” field on the output data.

I feel like the salesforce action “New or Updated File on Record” is broken/bugged if you cannot reference the file that fired the trigger.

The workaround seems to be to use a Find Record action after the initial trigger to find the content document that triggered the Zap, then use that since the file field does exist there. Still seems broken since you need an extra Zap.

 

Reply


Terms & Conditions