Zapier works by connecting to your apps and services to receive and send data. When an app's server responds to a request from Zapier, a HTTP status code is sent to Zapier. You might see an error code when you create a Zap or look at your Zap history.
General troubleshooting tips
Take these steps to troubleshoot errors you encounter in Zapier:
-
Turn the Zap off, then on again.
- This resets the Zap and can resolve some errors.
- Troubleshoot your Zap run errors with AI. You can use AI-powered troubleshooting from within your Zap run errors to explain the issue and provide step-by-step instructions to resolve it.
-
Check that all Zap fields are entered correctly.
- Check that all required fields are filled and that you used the right data formats for each field type.
- You can use the Formatter tool to change data formats or add a default value as a fallback whenever your mapped fields don't send data..
-
Check your app connection and account permissions.
- Confirm that your app account has been connected properly to Zapier and that you have the required permissions for the Zap to work.
- Search for the app’s How to get started page in Zapier’s Help Center to find information about how to connect.
-
Wait and try again later.
- Some errors are temporary and will resolve on their own.
-
Load a new trigger test record, then set up your action steps again.
- If your trigger isn’t sending data, it could be that the trigger fields have changed.
- Double-check that your mapped fields are also up-to-date.
- You can change or edit your test record to load fields and values you need.
-
Check your filter and path conditions.
- Ensure you’re using the correct filter and path rules.
-
Read the app help docs.
- Search for the app in Zapier’s Help Center to learn more.
-
Find a solution in the Zapier Community.
- Browse the Zapier Community for questions and answers from other users.
- Ask questions about the specific error you’re encountering and learn more about the apps that you’re using.
-
Check the Zapier Status page for any outages.
- It lists any downtime at Zapier due to things like scheduled maintenance or outages.
Error codes & messages
HTTP status codes that begin with a 4 or 5 (401, 504, etc.) are error codes.
400-series error codes
Error codes between 400 and 499 are client errors, which usually happen when the error occurs on your end. This is usually caused by issues with the data you're sending, or missing account permissions or authorizations.
500-series error codes
Error codes in the 500 series are server errors, which happen when an app’s server is down or experiencing other issues.
Other error codes
You may see a status code that’s not included in the list above. These are non-standard status codes and are likely specific to the app you’re connecting to Zapier. If you encounter one of these errors, reach out to the app’s support team for assistance.
Other error messages
You may also encounter an error message that doesn’t include a status code at all. Search for the error in Zapier’s Help Center or the Zapier Community for more info. If you still need help, reach out to the app’s support team for assistance.
I want my Zap to continue running even when there are errors.
Your Zap will automatically turn off if 95% of its runs result in errors in the last 7 days.
If your account is on a Team or Company plan, Zapier will send you an email notification to the account owner and provide a grace period before turning off your Zap. Company plan accounts have a 72-hour grace period and Team plan accounts have a 24-hour grace period.
If you have a Zapier for Companies accounts, you can override the high error ratio setting for an individual Zap.
If you need additional help with errors, contact Zapier Support.
