This validator compares a declared field map with one local, redacted JSON sample. It replaces the old friction score: a point total cannot determine whether identifiers, required values or date formats are correct. A passing sample is not approval to launch a Zap.
INPUT → RULES → LOCAL RESULT
Local integration field-mapping validator
Check an explicit map against one redacted JSON sample. Types stay strict; leading-zero IDs remain strings. No API request or guessed mapping is made.
The example ID is the text "00123", not the number 123. Clear the examples before entering your own redacted sample.
Enter the scenario to see a result.
No account connection, upload or automatic storage. Inputs are used only in this page. Use redacted test data; never enter credentials or signatures. Closing or reloading clears session entries.
Declare the map instead of guessing it
Each rule identifies a source using JSON Pointer, names the destination field, states its type and explicitly marks it required or optional. Nested source /customer/id is different from a literal key containing a slash, which needs the ~1 escape. The tool follows only your declared path; it never chooses a similarly named field.
Supported types are string, number, integer, boolean, object and array. Values are not coerced. Text "00123" remains text with its leading zeros; a numeric field containing the number 123 does not become that identifier. Large exact identifiers should be strings, because JavaScript cannot preserve every integer beyond its safe range. Such numeric samples are rejected instead of silently rounded.
Missing, blank and mismatched are separate outcomes
A missing required source fails. A present required null or blank string also fails. An optional missing source is labeled missing, while an optional blank is labeled blank. Neither is silently replaced by a default. This sample checker treats null as blank; it is not a full JSON Schema implementation and does not model a destination’s nullable-value rules.
The example maps four fields, including a string ID, a numeric amount and an optional blank note. Change /id to an absent path to see a required-source failure. Change its declared type to number to see a strict mismatch. Arrays can be addressed by an explicit index, but the checker does not iterate or infer line-item mapping.
Formats are explicit and limited
Optional format: "date" requires a real calendar date written YYYY-MM-DD. datetime requires a valid date/time with seconds and a Z or numeric offset; decimal accepts an ungrouped decimal representation. Unknown formats stay unresolved. Locale-specific commas, currency symbols, spreadsheet date serials and ambiguous dates are not guessed or converted.
Use Zapier’s field mapping instructions to inspect actual available fields, and obtain the exact destination schema and constraints from its vendor. A record matching these local rules still needs connector, permissions, deduplication and representative-record tests in the real workflow. The API capacity worksheet addresses a separate throughput question.
Method and limits
This is original local sample validation, not a Zapier API connection or live integration test. Limits are 250 KB per JSON input, 10,000 values, 20 nesting levels and 100 mapping rows. Inputs are not automatically stored or uploaded; use redacted test records. Browser print can preserve the visible worksheet at your request. Sources checked October 15, 2026: RFC 6901 and the linked Zapier field-mapping documentation.