The proposed solutions are cumbersome, though.
Best answer by SamB
Hey
I came across your question and it inspired me to do some digging into other potential workarounds. And I found a way to see how many reactions there have been using webhooks. Essentially you’d use a GET request to connect to Slack’s reactions.get endpoint and see the current count of reactions on a specific message.
I wrote up a quick guide on how to do it here:
Not sure if it’s much less cumbersome than the other suggestions, but hopefully it’ll be helpful! 
+14Hi
An alternative approach would be to log each Slack New Reaction Added in a GSheet or Airtable, then check against that each time to determine if the Zap should proceed by passing thru a Filter step.
An alternative approach would be to log each Slack New Reaction Added in a GSheet or Airtable,
Hi Troy :-)
That’s exactly what I had in mind with “cumbersome” 
+11Hey
I came across your question and it inspired me to do some digging into other potential workarounds. And I found a way to see how many reactions there have been using webhooks. Essentially you’d use a GET request to connect to Slack’s reactions.get endpoint and see the current count of reactions on a specific message.
I wrote up a quick guide on how to do it here:
Not sure if it’s much less cumbersome than the other suggestions, but hopefully it’ll be helpful!
Hi
For me, this is less cumbersome, because the work is done in one place, and there’s no separate spreadsheet to be documented and risk falling out of sync.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
