Skip to main content
Best answer

Slack "Find Message" step no longer finds bot messages (Include Bot Messages is set to Yes)

  • June 29, 2026
  • 10 replies
  • 125 views

Hi Zapier Support Team,

First of all, thank you for your great service! I have been using this automation flawlessly for about 3 months.

However, since last weekend, my Slack automation has stopped working. After running several tests, it appears that the Slack "Find Message" step is completely ignoring messages sent by a bot.

For context, my workflow is:

  1. Trigger: New Reaction Added (Emoji) in Channel A.

  2. Action: Find a specific thread created by a bot in Channel B using search keywords.

  3. Action: Forward the reacted message as a thread reply to that bot's thread.

While troubleshooting, I discovered that the "Find Message" step successfully finds messages sent by human users containing the keyword, but it consistently fails to find the bot's messages containing the exact same keyword.

Please note that I definitely have the "Include Bot Messages in Search Results?" option set to "Yes".

Could you please let me know if this is a known issue or if I am the only one experiencing this? Was there a recent update on Zapier's end regarding the Slack integration that might have caused this?

I would appreciate a thorough review of this issue and any workarounds or solutions you can provide.

Thank you!

Best answer by SamB

Good news everyone, the bug has been fixed! 🎉

The issue was caused by a recent change on Slack's side in how the search.messages endpoint handles the parameter that controls whether bot messages are included in search results. Our engineers have updated the Slack app integration to send the value in the format Slack now expects, so now bot messages will once again be returned when the "Include Bot Messages in Search Results?" setting is set to Yes.

To take advantage of the fix they shipped, you’ll need to update your Zap to use the latest version of the Slack app. See our guide on How to update to the latest app version for instructions on how to do that.

Thanks so much for your patience while this was being worked on. Let us know if you run into any trouble upgrading, want to make sure you're all set!

10 replies

Forum|alt.badge.img+4
  • Zapier Solution Partner
  • June 29, 2026

Hi ​@soojung 

You can try these: 

  • Use Slack's from: Search Modifier
    Force the search to look specifically for messages from the bot. In your "Find Message" step, modify the "Search Query" to include from:<@BOT_USER_ID> or from:@BotName before your keyword. This tells Slack to prioritize messages from that specific bot.

  • Use the "Get Message" Action
    The "Find Message" action relies on Slack's search.messages API, which is a legacy method and is being deprecated. This is likely the root cause of the issue, as changes to this API can break functionality at any time. Zapier introduced the "Get Message" action as a direct replacement for fetching messages by their unique ID

How to implement it:

  1. Replace the "Find Message" step with the "Get Message" action.

  2. You will need the Channel ID and the Message Timestamp.

  3. If you have the message's permalink URL, you can use Zapier's Formatter steps to extract the timestamp and convert it to the required Unix timestamp format

Here's the doc that might help:

Hope this helps you get it sorted! 

If you're still running into issues after trying these steps, feel free to drop a screenshot of the error, zap configuration and a quick description of what your Zap is doing—happy to take a look and help troubleshoot.


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • June 29, 2026

Hi ​@soojung, welcome to the Community! 🎉

I couldn’t see any recent updates to the Slack app that would have affected the Find Message action, and didn’t find any bug reports open for this at the moment. There’s sometimes a small delay after a bot message is created before it is searchable, so if the bot message was being searched for shortly after it was posted then that might be why the Zap didn’t find it. If that’s the case, then adding a Delay step to the Zap may help the Find Message action to find the message.

If it can’t find older messages either, then it could well be a bug, especially since it was working fine until last weekend. 🤔 In which case, I’d recommend reaching out to our Support team so they can investigate further. 

Keep us posted on how you get on!


  • New
  • June 30, 2026

I have the same issue - a step that used to work fine, suddenly stopped performing as expected.

I can use the same search querry in the Zapier step and directly in my Slack app, and the Slack app returns the results, while the Zapier step does not.

I’m attaching the results and exact settings.


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • June 30, 2026

Sorry to hear you’re running into this as well ​@Talkie.ai.

Looks like our Support team has since opened a bug report for this, so I've added you both to the list of folks being affected. We can't share an ETA, but we'll email you once it's fixed.

Thanks for your patience in the meantime. 🙏


  • New
  • June 30, 2026

@SamB can you please add me to the list as well? I’m having the same issue & would like to know when it’s fixed. Thanks!


  • New
  • July 1, 2026

@SamB Same here, zaps are showing the same issue, and we have confirmed that it only affects bot messages. 


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • July 1, 2026

Thanks for letting us know ​@ea814e and ​@Karim A. I’ve added you both to the list so you’ll get a notification as soon as it’s sorted. And I’ll be sure to follow up here with any news in the meantime.

 


  • New
  • July 1, 2026

Please add me as well. This is severely affecting some very important flows that we have trigger 20+ times a day for important business operations. 


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • July 2, 2026

Really sorry to hear that ​@rbs777. I do hope the team will be able to get things sorted soon. 🤞

I’ve added you to the list. We’ll be in touch by email once it’s sorted.


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • Answer
  • July 3, 2026

Good news everyone, the bug has been fixed! 🎉

The issue was caused by a recent change on Slack's side in how the search.messages endpoint handles the parameter that controls whether bot messages are included in search results. Our engineers have updated the Slack app integration to send the value in the format Slack now expects, so now bot messages will once again be returned when the "Include Bot Messages in Search Results?" setting is set to Yes.

To take advantage of the fix they shipped, you’ll need to update your Zap to use the latest version of the Slack app. See our guide on How to update to the latest app version for instructions on how to do that.

Thanks so much for your patience while this was being worked on. Let us know if you run into any trouble upgrading, want to make sure you're all set!