Slack error: Nothing can be found for the search
- Tables
-
Product updates
Product updates: January 2023 Product updates: March 2023 Product updates: February 2023 Product updates: April 2023 Product updates: May 2023 Product updates: June 2023 Product updates: July 2023 Product updates: August 2023 Product updates: September 2023 Product updates: October 2023 Product updates: November 2023 Product updates: December 2023 Product updates: January 2024 Product updates: February 2024 Product updates: March 2024 Product updates: April 2024 Product updates: May 2024 Product updates: June 2024 Product updates: July 2024 Product updates: August 2024 Product updates: September 2024 Product updates: October 2024 Product updates: November 2024 Product updates: December 2024 Product updates: January 2025 Product updates: February 2025 Product updates: March 2025 Product updates: April 2025 Product updates: May 2025 Product updates: June 2025 Product updates: July 2025 Product updates: August 2025
- Zaps
- Your Zapier account
- Interfaces
- Canvas
- Chatbots
- Getting started
- Agents
- MCP
- Built-in tools
- Lead Router
- Apps
Table of Contents
When using Slack’s search action in your Zaps, you get the error message “Nothing could be found for the search.” You’ll see this error while testing your Slack step or in the details of a Zap run.
Causes
This happens when:
- The message you are searching for does not exist in Slack.
- The search query does not match the corresponding messages in Slack.
- The search modifiers restrict your search results or have been set up incorrectly.
- The mapped field used to identify the username contains blank spaces (whitespace).
How to fix
To fix it:
Find Message action Find Username action
Find Message action
- For your affected Zap run, check the message you’re searching for exists in Slack.
- Go to your affected Slack step.
- Check the Search Query field to ensure it uses supported Slack modifiers.
- Ensure the Sort By field is set up for your expected results.
- Match Strength (sort by most relevant message)
- Message Date Time (sort by most recent message)
- Check that the Sort Direction field is set the way you expect.
- Descending (most recent or best match first)
- Ascending (oldest or worst match first)
Find Username action
This search action often errors because there are white spaces within the field mapped. To check for white spaces:
- Go to your affected Zap run.
- Click the action step where the mapped field with the username comes from.
- Review the Data Out tab.
- To check for whitespaces, highlight the field by clicking and dragging your cursor over the text. This will make extra white spaces more noticeable.
- If the field contains additional whitespaces, you can add a Formatter step to remove extra text.

You can use the procedure of highlighting the content of a field to check for white spaces when testing the step.
Still need help?
If this article did not fix the issue, Zapier has a few other options to get you the help you need:
- Contact Zapier Support. Our Support team can investigate your account to find solutions.
- Ask in the Zapier Community. Get advice from experienced Zapier users in the Zapier Community.
- Learn more about getting help. Read our guide on how to get help and support with Zapier to find the best resources for your specific problem.