I would like to be able to trigger an external webook when something is added or changes in smartsheets. I use make.com and would like to be able to send shartsheet data to a make.com webhook as an automation action.
Sign in to see the current vote count, add your own vote, or leave a comment.
TLDR: I would love to be able to create a simple automation on a Smartsheet that after a trigger a webhook could be send.
Story: I am trying to use Zapier to integrate Smartsheet with our business processes. My issue has been the trigger (= Updated Row) and the delay (or even absence). Sometimes it takes a few minutes, sometimes 10-15, even up to 30 min, but some do not even make it to my Zap. I tried to create a webhook through Smartsheet API (with AI help), but I couldn't get it to work (I don't have any coding/programming background).
I have made a work around using the Smartsheet automation to send an email to my inbox after a particular row (in a certain column) is updated. So now the trigger for my Zapier automation is receiving an email and this works great! But I have created an unnecessary in-between step. So: I would love the basic Smartsheet automation on the spreadsheets to allow for a Webhookto be send directly to Zapier. It would make this whole process easier and more reliable and not need to use the Smartsheet API developer tools.
Thanks!
I have a workflow with nearly 40 automations, half of which are email-based requests for updates with various sets of triggers. While I know the automations work, due to months of testing, when our system went live to the institution, I became very worried that the automations wouldn't run and I'd have no idea whether or…
Hi, I am part of a very large organization where hundreds will have Admin access to hundreds of Workspaces in order for them to contribute and make full use of Smartsheet features. Currently All Smartsheet workspace Admins receive Workspace access email alerts. Which means hundreds of team members will effectively be…
It would be useful if users who clicked a Dynamic View link (that they were not previously added to) could "request access" to the Dynamic View, and provide a reason, so that the admin can easily grant that access. The use case for me would be to avoid having to pre-populate and then maintain a user group of viewers, but…
