Sometimes you might get an error that says a record is not found. You’ll see these errors either after testing an action step or if you’ve already turned your Zap on, in the Task History. This can happen for a few different reasons.
Fix "Not found" errors in Zaps
If you’re trying to update a record that exists in another app, but you’re getting the “not found” error in the action step, it could be that the record you’re trying to find or update does not exist.
For example, if you’re trying to update a contact in Salesforce, make sure that the contact you’re trying to update already exists in Salesforce.
If you’re using custom values to find and update a record, make sure that you’re using the right value.
Similarly, if you’re using a search step, make sure that you’re searching for the right value.
Learn more about custom values steps.
If your Zap is creating a new record in one step and then later updating or referencing that same record in a later step, you might need to add a delay step in order to give the app time to create that new record.
For example, if we have one step that creates a new card in Trello from some data and then a later step that moves that same Trello card to a new column, we may need to add a delay step in between to give Trello time to make the card.
If you're having troubles with this workaround, contact Zapier support.
Need More Help?