Zapier errors
Common Zapier errors, grouped by component. Open one for the exact error text, its likely causes, the fix and the official documentation.
- Errors
- 28
- Components
- 16
- Verified
- 28
- Official docs
- help.zapier.com
28 errors in 16 groups
Action step fields1
Action steps2
- Not foundA "Not found" error in a Zap means the record the step is updating or finding does not exist in the app. Check that the record exists, check the custom value or search criteria, and add a Delay step if an earlier step creates the record.
- Required field is emptyA Zap errors this way when a required field in an action step receives no value, usually because the mapped field from an earlier step is optional. Map required fields to fields that always have a value, or add a default value with Formatter.
API by Zapier4
- 401 or 403 errors in API by ZapierA 401 or 403 from an API by Zapier step means the credentials expired, were revoked, or lack the permissions or scopes the endpoint requires. Create a new connection with updated credentials and confirm the permissions with the API provider.
- 4xx or 5xx errors from the API in API by ZapierThese status codes in an API by Zapier step come from the API being called, not from Zapier. Check the endpoint URL and request against the provider documentation, add a delay for rate limits, and retry later for 5xx errors.
- Domain not allowedThis API by Zapier error means the domain in the step URL does not match the domain filter set when the connection was created. Compare the two, use a wildcard for subdomains, or create a new connection with the correct domains.
- JSON errors in the request bodyA JSON parsing error in an API by Zapier step means the request body is not valid JSON. Validate the body, quote mapped fields properly, and escape special characters with a Formatter step.
App connections1
Code by Zapier2
- Scripting payload too largeThis Code by Zapier error means the code and the data it processes exceed the 6 MB I/O limit of the Code step environment. Return only the keys you need, and filter or trim large API responses before returning them.
- You cannot return more than 250 items from a Code actionThis Code by Zapier error means the step returned more than the 250 items allowed in the output object. Return 250 items or fewer, or split the work across several Code steps.
Code by Zapier (JavaScript)1
Code by Zapier (Python)1
Connected app requests1
HTTP status errors7
- 400 - Bad RequestA 400 in a Zap means the server could not understand the request due to invalid syntax. Check for missing values in required fields, invalid characters and incorrectly formatted input.
- 401 - UnauthorizedA 401 in a Zap means the request lacks valid authentication credentials. Reconnect your app account by disconnecting and then reconnecting it.
- 403 - ForbiddenA 403 in a Zap means the server understood the request but refused to fulfill it. Confirm the app account is connected properly and has the required permissions.
- 404 - Not FoundA 404 in a Zap means the server could not find the resource you requested. Check that the record exists in the app and that the search criteria are right.
- 422 - Unprocessable EntityA 422 in a Zap means the request was well-formatted but contained errors that prevented the server from fulfilling it. Check that required fields have values in the right format.
- 429 - Too Many RequestsA 429 in a Zap means too many requests were sent in a short period and exceeded the rate limit of Zapier or the app. Review the rate limits, then replay the run or add a delay.
- 500 - Internal ServerA 500 in a Zap means the server encountered an unexpected condition, with a variety of possible causes in Zapier or in the app. Replay the failed runs if it happened only a few times, and check the status pages if it happens on every run.
Rate limits1
Replaying Zap runs1
Zap history1
Zap on/off state1
Zap run status1
Zap step processing1
Zapier SDK in Code steps2
- Authentication failed (Zapier SDK in Code steps)This error in a Code step that uses the Zapier SDK means the app connection used by the SDK has expired or been revoked. Reconnect the app connection in the Zap editor and confirm it is active.
- Connection not found (Zapier SDK in Code steps)This error in a Code step that uses the Zapier SDK means no connection is selected in the connection picker, or the appKey in the code does not match the connected app. Select the right connection and verify the appKey.
More for Zapier work:Open Zapier jobsZapier rates and salaries
The iPaaS Brief
Subscribe to The iPaaS Brief.
The iPaaS newsletter for the people who run integrations. From iPaaS Group.
Free. You finish on theipaasbrief.com and confirm by email.