Smartsheet "update" broke my Zapier workflows - need solution ASAP

Hi ​@AWSNAweb 

The Zap trigger is a webhook.

Make sure to test by performing the event (update a row) in Smartsheet.

Then in the Zap trigger step, on the TEST tab, pull thru new examples to use to configure the Zap action steps.

Hi Troy, thanks for your reply!

So are you saying that the nature of the Smartsheet “Update Row” zap has changed to being a webhook?  I haven’t worked with webhooks yet, I will need to research how to use/build zaps with them… was there any announcement about this change anywhere?! 

​@AWSNAweb 

Webhooks are instant.

Origin app sends data to a url when an event happens.

In this case, Smartsheet sends data to the Zap trigger webhook URL when a row is updated.

So in order for you to have real data to use to configure the Zap action steps, you need to update a row in Smartsheet, then in the Zap trigger, go to the test table, and use the button to pull thru recent examples.

Select a recent example, then update your Zap action steps.

Ok, so… when I “update row” in Smartsheet, I need it to send all of the mapped data fields to iMIS to create a new row in a panel. Any one of those Smartsheet data fields (let’s say there are 9) could change, even several of them at once, but not always the same field.  How would I set up the webhook?  If I need to specify a single, specific field as the trigger for the webhook, this becomes a problem, doesn’t it?  And.. how many Zaps are used with a webhook + data?

I am having a very similar issue with updates to Mailchimp from Smartsheet. The legacy version worked fine but this new instant version doesn’t update any of my fields (it won’t let me map anything either) and my zap won’t stay powered on. Need help ASAP. (I also submitted my own ticket but saw this thread with a similar issue to mine!)

Thanks for adding your comment, ​@hr-irle - makes me feel like I’m not alone (and not crazy!). 

It seems that whoever created this “update” fixed one problem (in our case: any time some change was made in a row, it would trigger the zap and all of the information would send, which for us created multiple duplicates… a headache for sure), but the “fix” (defining ONE trigger field only, and no field mapping) didn’t take into consideration how this would affect all of the Zaps already written that need all the mapping.  SO FRUSTRATING.

Hi ​@AWSNAweb,

A recent Zapier update has changed how triggers function, limiting them to a single field without mapping options and disrupting workflows that relied on multiple-field monitoring. While this update may have been intended to reduce duplicate triggers caused by any row change, it has introduced new user complications. To adapt, reviewing and adjusting affected Zaps is recommended, as well as adding filters to control when they run or using additional tools to restore lost functionality. Providing feedback to Zapier can help highlight the impact of these changes, and engaging with the Zapier Community remains a valuable way to find alternative solutions and share experiences.

Please feel free to contact us if you have specific questions or need more detailed guidance on adjusting your Zaps. We're here to help you find a solution that meets your needs.
 

@JammerS - Beyond posting in this Zapier Community, what’s the best way to provide feedback directly to Zapier? I gotta get this sorted REAL Fast!

Hi ​@AWSNAweb,

If you need to share feedback or get urgent help from Zapier, you can contact their Support team through the Contact Support page to submit a detailed ticket. For faster assistance, use the live chat feature.

I’m having a similar issue and most likely the Smartsheet update was the culprit that killed my zaps. I have three zaps dependent on the option for “All” to go with the Smartsheet but it no longer brings the “All” to the new Workspace when it’s copied and created a new project plan for a team member. I’ve submitted my request/situation to the support email for Zapier. I’m digging into the workaround with the webhook, but I hope they roll back whatever changes were made. Has anyone who has been successful with setting up the webhook have any tips or tricks to share?

I was able to resolve my issue by adding another task to my automation workflow and updating to the new Update Row. It’s working great but it’s a bummer to have to add another task to each of the three workflows. Because All no longer covers Share on its own, the added task counts as one more against the monthly allowance for each flow, three in total. If there is a way to get All to work without the extra task, let me know! 

Hi ​@AWSNAweb,

Thank you so much for sharing this information. This will significantly help our Community members with the same issue.