Pipedrive error: Nothing could 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 any of Pipedrive search actions in your Zaps, you see the error message "Nothing could be found for the search". You may see this error when setting up a Zap or in the details of a Zap run in your Zap history.
Causes
This happens when:
- The mapped field from the previous step contains text instead of an ID that Pipedrive expects.
- The mapped field data does not exist in Pipedrive when searching for text.
- You attempted to search for data within a custom field type that Pipedrive does not support. For searches, Pipedrive only supports text, large text, numerical, monetary, autocomplete, phone, and address type custom fields.
- You used an exact match search, which restricts your search results. This means it can be affected by the case, spelling, punctuation, spacing, special characters, and word order.
How to fix it
To fix this issue, in your Pipedrive search step:
- Ensure the Field to Search By field contains a supported field type and has not been set as a custom value.
- You can also create a lookup table with the relevant Pipedrive IDs to dynamically update the Field to Search By field using custom values.
- If you’re using exact match search, try using a broader search (fuzzy). This will allow the Zap step to find similar results such as closely related phrases or keywords. To enable fuzzy search:
- In the Search for an Exact Match? field, select No.
- If you must use exact match search, add a Formatter step to remove unnecessary formatting (e.g., extra spaces, special characters) from the search query to improve matching accuracy.
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.