Best answer

New Saved Message Slack trigger does not work anymore after Slack update



Show first post
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

69 replies

I received an email today saying that the issue was fixed: 

You're receiving this notification because you showed interest in a reported issue with our Slack integration. The issue was related to the “New Saved Message” trigger not working in certain cases. We wanted to let you know we worked with our partners at Slack and this trigger should now be working as expected.

There’s no specific action you need to take, but if there were some Zaps you were holding off on making because of this problem, now you can!

Don’t hesitate to get in touch if things aren’t working like you expect, or if you run into any other issues. We’re always here and happy to help! Have a great day!

- Alejandro

 

But it is still broken. Can you confirm this is fixed, @SamB ?

I don’t think it has. Currently not working for me. 

Userlevel 7
Badge +9

Ah, thank you @alexisg! So nice to still see you in these parts still dropping knowledge bombs. 🎉 

Thanks @julip! I’ve added ya - I wonder if in the meantime giving @alexisg workaround a shot might do the trick though? 

Let us know!

 

This post has been edited by a moderator to remove personal information. Please remember that this is a public forum and to remove any sensitive information prior to posting.

Hey @Admin Bpo I’m having the same issue.

 

@Charie would you mind adding email to that bug report?

 

Thanks!

I’m also struggling with this change/bug

Please add my email to the bug report as well, thank you!

Userlevel 7
Badge +9

Thank you - ya’ll are both good to go!

Userlevel 3
Badge +4

Hi @Jpez 

I have also added your email address to the bug report.

Let me know if you have other questions! 😊

Userlevel 7
Badge +11

YAY! Glad to hear it’s working for you @bwtobias! 😁

As some users are still experiencing issues it appears that it’s not been fully resolved just yet. I don’t have any ETAs I can share on when it’ll be but we’ll be sure to keep you all in the loop on any news on that here.

Thank you all for your patience here! 🙏

Userlevel 7
Badge +9

Ah, sorry to hear that, @hunor6. I’ve got you added and we’ll email you once a fix is in place!

Userlevel 1

@petethezapper just an fyi that if you leave the `channel` filed blank when creating a reaction based Slack message it will work for any channel in your Slack instance.

Userlevel 1
Badge

@petethezapper just an fyi that if you leave the `channel` filed blank when creating a reaction based Slack message it will work for any channel in your Slack instance.

OOohh, this is perfect!  It works with any channel if I leave that blank, however if I leave User blank, it doesn’t seem to work at all for reactions to DM’s.

Userlevel 1
Badge

Thank you for sharing this, @petethezapper! Beat me to it. 🔥

As the email mentioned, our team is in touch with Slack and we’ll be sure to keep ya’ll updated with any news.

I know it’s not ideal but we absolutely appreciate ya’ll bearing with us. 🙏🏽

OK, so I was all about this option and I even created a custom Todoist icon emoji. But the problem is that if any other Slack user also uses this reaction, then it’s gonna trigger this Zap, correct?

Can I please also be added to the bug report

Userlevel 1
Badge

Thank you for sharing this, @petethezapper! Beat me to it. 🔥

As the email mentioned, our team is in touch with Slack and we’ll be sure to keep ya’ll updated with any news.

I know it’s not ideal but we absolutely appreciate ya’ll bearing with us. 🙏🏽

OK, so I was all about this option and I even created a custom Todoist icon emoji. But the problem is that if any other Slack user also uses this reaction, then it’s gonna trigger this Zap, correct?

 

Yup, confirmed, it’s when anyone uses the reaction. Not going to work for me.

Can you please add my email too as I have the same issue and the workaround does not work either.

Mine was working only yesterday then decided to stop.

If you can add me too that would be great

@alexisgok, so just to clarify with this new action, you have to click the three dots button in Slack, select “Push to Zapier”, choose the option to select the zapier zap from the dropdown and click Push?

Damn, so many steps now. :/

I do like that you can add in additional notes though

 

Userlevel 7
Badge +9

You’ve been added, @treebranchmedia!

Userlevel 7
Badge +12

@julip, I’ve added you to the bug report. In the meantime, @alexisg has posted a great workaround that you can try. 

Thanks!

Userlevel 7
Badge +11

Hi friends! 👋

@radmartin and @Grzegorz, I’m happy to confirm that I’ve added you both to the list of affected users. We’ll be sure to contact all affected folks by email the minute it gets fixed.

@petethezapper and @everything_is_fine, on that workaround of using the New Reaction Added trigger, instead of filtering the user on the trigger, perhaps you could add a Filter by Zapier action to the Zap to handle the filtering?

That way the Zap would still to trigger for all reactions added but would only allow the Zap to continue if the User Id field (Text) Contains a specific Slack user ID. More information on how to set up filter rules can be found here: Customize your filter rules 

Hope that helps in the meantime! 🙂

Userlevel 1
Badge

 and @everything_is_fine, on that workaround of using the New Reaction Added trigger, instead of filtering the user on the trigger, perhaps you could add a Filter by Zapier action to the Zap to handle the filtering?

That way the Zap would still to trigger for all reactions added but would only allow the Zap to continue if the User Id field (Text) Contains a specific Slack user ID. More information on how to set up filter rules can be found here: Customize your filter rules 

Hope that helps in the meantime! 🙂

 

Thanks @SamB This would work, however I am on the free plan, so I cannot do multi-step Zaps.

Userlevel 7
Badge +9

Absolutely agree with ya’ll - not an ideal scenario. In the meantime though, I’ve got you both added and hopefully be able to share an update soon. 🤞🏽

Userlevel 1
Badge

For people who are hitting this issue, if you can use “New Pushed Message” instead, that trigger still works since it’s on-demand.

It’ll require you to remap fields in the action, since the structure of the data is a little different. In my case I had to switch over to fields under Message - Message Ts Time (timestamp), Message User Name (username), Message Text (text - this is probably the most commonly needed).

 

Zapier just emailed me with this option below. This isn’t a great alternative since it would only apply to the one Slack channel you specify. I’ll stick with the push option.

 

-------------------

We are writing to inform you of an important update regarding the Slack integration that you have been using. Recently, Slack has made a change to their API that affects the "New Message Saved" trigger in our integration. As a result, this trigger has stopped working. Our team is actively working with Slack to introduce a new, permanent solution.

We understand that this may have caused inconvenience to your workflow, and we want to ensure that you are aware of the issue and offer you an interim solution. We've identified a workaround for this issue, which involves using the "New Reaction Added" trigger and filtering it by a specific Slack user as shown here:

 

 

Userlevel 7
Badge +9

Ah, thanks for giving it a try and letting us know! Sorry to hear it’s not an option at the moment.

While I don’t have an ETA for a fix, I did add you to the bug report so we’ll email you once a fix is in place. 🙂

I have the same problem. Please add me to the bug report.