Zapier works by connecting to your apps and services in order to receive and send data. When an app's server responds to a request from Zapier, a HTTP status code is sent to Zapier. HTTP status codes that begin with a 4 or 5 (401, 504, etc.) are error codes. Learn what these error codes mean and how to resolve them.
Troubleshoot error codes in Zaps
1. 400 - Bad Request
Problem: your Zap is likely to be missing a required field, or a field value wasn't in a recognized format. For example, if a field in your action step is expecting an email address, but the value given is a name, the app may return a 400 error.
Solution: check that your fields are correctly set up and mapped to each other.
2. 401 - Unauthorized
Problem: Zapier can't connect to your app account because your password was changed, or Zapier's access was revoked.
Solution: reconnect your app account to Zapier.
3. 403 - Forbidden
Problem: the app account Zapier is trying to connect to doesn't have permission to complete this step. For example, you might have permission to add new contacts in your app account, but not to send emails to contacts.
Solution: contact your account administrator or ensure that you have the required permissions for the step.
4. 404 - Not Found
Problem: a field value used in this step is missing, or Zapier is unable to find the information in the app it's trying to connect with. For example, an action step set up to send an email to a contact who submits a form might encounter a 404 error if a contact doesn't include their email address in the form submission.
Solution: check that the information exists in your connected app and that the field values used in this step were mapped correctly.
5. 405 - Method Not Allowed
Problem: the app Zapier is trying to connect to is experiencing an unspecified problem.
Solution: contact Zapier support for help with resolving this error.
6. 408 - Request Timeout
Problem: the app Zapier is trying to connect to is too busy or temporarily unavailable.
Solution: timeout issues will often resolve on their own after a few hours. If the error persists, learn how to fix timeout errors.
7. 409 - Conflict
Problem: the record that you are trying to update or use in the app account Zapier is trying to connect to is currently in use, or is being updated elsewhere (often by another user in the app account).
Solution: ensure that the record is not currently in use, then try the step again.
8. 410 - Gone
Problem: data is missing in the app account Zapier is trying to connect to.
Solution: go through your Zap and ensure that all fields (especially any custom fields) are selecting options that exist in your app account, in case anything has been deleted, renamed. or moved. If you edit the names or availability of options in your app account, take note that it must be manually updated in your Zap as well so Zapier looks for current information.
9. 414 - URL Too Long
Problem: the URL being sent was too long, such as a URL many query parameters.
Solution: if you're using [webhooks in Zapier]((/tutorial/use-webhooks-in-zaps/), check that you're not adding too many values to the webhook URL.
10. 415 - Unsupported Media Type
Problem: the app account Zapier is trying to connect to was expecting a file of a certain type, but received a file of a different type.
Solution: check that any files sent in the Zap are using the correct file type. For example, ensure you're not trying to upload a video file when only PDF files are allowed.
11. 429 - Too Many Requests
Problem: Zapier has made too many requests to the app account it's trying to connect to. The Zap is likely asking for or sending information to the app too frequently within a given timeframe.
Solution: change your Zap to trigger on fewer items, add a filter to your Zap, or upgrade your app account to allow more API requests.
12. 500, 501, 502, 503 - Server errors
Problem: 500-503 errors are the most generic 500 series codes and can happen when an app’s server is down or experiencing other issues.
Solution: check Zapier's status page and the app’s status page for information on on outages, maintenance, or downtime. If there is no relevant information, reach out to the app's team, or wait for the error to resolve.
If the 500 error occurred on your trigger app, no further action is needed because your Zap will run properly the next time Zapier can successfully poll the trigger. If the 500 error occurred on your action app, you can manually replay affected tasks.
13. 504 - Gateway Timeout
Problem: Zapier is likely trying to work with a large amount of data or upload a large file. If the 504 error is occurring in your Zap trigger, it’s likely that there is more data (e.g., a large spreadsheet) than Zapier is able to obtain in the timeout window.
Solution: reduce the amount of data that is used in your Zap trigger or uploaded to your app account.
If you're not able to resolve the error codes after taking the steps in this article, contact Zapier support for further assistance.
Need More Help?