Fix "Not found" errors in Zaps
- 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
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 your Zap History. This can happen for a few different reasons.
1. Check if the record exists in your app
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.

If you’re trying to update a contact in Salesforce, make sure that the contact you’re trying to update already exists in Salesforce.
2. Check your custom value or search criteria
If you’re using custom values to find and update a record, check if you’re using the right value.
Similarly, if you’re using a search action, check if you’re searching for the right value.
3. Add a delay step
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 you have an action that creates a new card in Trello from some data and a later action that moves that same Trello card to a new column, you may need to add a delay step in between to give Trello time to make the card.
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.