When using a Salesforce search action in your Zaps, you get the error message “Nothing could be found for the search.” You’ll see this error in the details of a Zap run in your Zap’s history. 

Causes

This happens when:

• The object you are searching for does not exist in Salesforce or another Zap that should've created it has not created it yet.
• The search criteria for an object does not match the corresponding data in Salesforce.
  • You have selected the wrong Salesforce Object.
  • The mapped field in the Search Value field contains data in a format different from that in Salesforce.
• The mapped field from the previous step is blank.
  • Salesforce requires a value in the Search Value field to search.

How to fix

To fix it:

Check in Salesforce that the object you are searching for exists.

• If the search action supports creating an object if one is not found:
  • Go to your Salesforce search action.
  • In the Configure tab, select the Create if Salesforce record if it doesn’t exist yet? Checkbox.
  • Complete any fields you need for a new record.
• If your search action does not support creating an object if one is not found, you can instead add branching logic with paths to your Zap.
  • Create one path that continues if an object is found, then proceeds through the rest of your Zap steps.
  • Create a second path that continues if an object is not found. Then, add a create step to create your object. Finally, copy and paste the rest of your Zap steps.
• If your object is created by another Zap that runs after your affected Zap, add a delay step prior to your Salesforce search action. This will prevent your Zap from running until the object is created.

Review your Salesforce search action. 

• Ensure the object type you selected to search by is correct and matches the corresponding data in Salesforce.

Review the mapped field you are using in your search field. 

• You may need to map a different field that has values that match object IDs in Salesforce.
• If the field you mapped from a previous step does not always send a value,  replace it with a field that consistently does. If you cannot change the current mapped field:
  • Add a step to set a default value as a fallback whenever your mapped field has no data.
  • Add conditional logic using a filter or branching logic with paths before your search step. This will allow you to define what the Zap should do if the mapped field receives no data from the previous step.
• (Optional) You can format data in your mapped field using Formatter by Zapier to match what Salesforce expects. Learn more about:
  • Getting started with Formatter.
  • Split text fields
  • Modify text formats

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.