Zapier · Action step fields
Zap field will not accept your data
Short answer
A Zap field rejects a value when the value does not match the format the app expects, such as a date format, a field name instead of an ID, or an image name instead of a file. Check the field help text and send the value in the expected format, using Formatter where needed.
VerifiedLast verified
01Error text
An error referring to a value format02Likely causes
- The value (static or dynamic) does not match the app's expected format.
- Examples are a date format different from what the app expects, a field name instead of a field ID, an image name instead of a file object or public URL, or a fake email address.
03How to fix it
- Open the Configure tab of the affected step and review the field's expected format and help text.
- Enter the value in the format the app expects.
- Modify the value with Formatter (date/time, number, text, utility).
- For custom values, find the app's expected ID and, if needed, create a lookup table.
- For images, send a file object or URL to a file field.
iNotes
Zapier does not quote a fixed message for this problem. The text above is its description of the error.
04Official documentation
→Related errors
- 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.
- 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.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Zapier work:Open Zapier jobsZapier rates and salaries