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 designed to created a row in Google Sheets when a new message is posted in a Slack channel. This has been working for years. At the end of last month, it stopped working. There have been multiple messages posted to this Slack Channel in the last week that have not created a new row. I am on the Free plan and have not exceeded the monthly limit. I looked at the Zap history, and it does not show any runs failed or are paused. Seems like it is just missing the trigger Slack messages. Please help.

Hi ​@Clay House Photography 

Help link for things to check/try to troubleshoot why your Zap trigger step is not triggering: https://help.zapier.com/hc/en-us/articles/8496199211277-Zap-isn-t-triggering

Laura at Zapier Support happy to help.

I've looked into this and found that you're experiencing a known issue with the "New Message Posted to Channel" trigger.

This is a documented bug that affects certain public channels, particularly those that were previously private or are part of Slack Connect. The trigger can stop working properly with these specific channel configurations.

 

Here's the alternative to get you back up and running:

  1. Edit your Zap and change the trigger from "New Message Posted to Channel" to "New Message Posted to Private Channel"
  2. Select your channel from the dropdown menu
  3. If your channel doesn't appear in the dropdown, you can manually enter the channel ID instead

 

This alternative trigger should work reliably with your channel setup and get your Zap triggering again on new messages.

 

I know this isn't the ideal solution since you're dealing with what appears to be a public channel, but this workaround has proven effective for similar cases. Our engineering team is aware of this issue and working on a permanent fix.

 

Let me know how this works for you, and I'm happy to help with any questions about implementing the alternative!

 

Best,

Terms & ConditionsAccessibility statement