Short answer
Missing fields, null, empty text, zero and false should not automatically be treated alike. Define preserve, clear or update under the API contract. Test each on a fictional record and check the destination rather than only the module’s displayed value.
Key verification: All five cases meet the contract and zero or false are not unintentionally replaced by defaults.
Sources and limitationsAn update without a phone field erases an existing number; another replaces zero quantity with the prior value. Both may arise from a generic empty-value rule. This guide proposes a field contract and a small test without altering real CRM data or claiming a universal connector formula.
Define intention before mapping
| Fictional input | Proposed meaning | Contract result |
|---|---|---|
| Missing field | No update to that field | Preserve |
| null | Explicit clear request | Clear only if API supports it |
| Empty text | Invalid data in this example | Review |
| 0 | Valid quantity | Save zero |
| false | Disabled option | Save false |
These are exercise rules, not guaranteed API behaviours. Some APIs do not clear with null; others omit empty fields. Separate type from presence before sending. The string “0” is not necessarily numeric zero either: validate the destination type.
Documented Make functions
Make documents ifempty, omit and the erase keyword, with different effects. Field type affects erase. Check definitions and actual module output rather than using a function name as evidence of how an API handles a request.
Small reversible test
Create a fictional record with known values and apply all five inputs separately. Retain sent body, response and subsequent record reading. Reset to the same initial state: testing on the prior case’s leftovers obscures errors. Avoid keys or personal data in screenshots.
Accept without false universality
CallsIQ has not run this Make test. Acceptance requires expected changes and no accidental clearing; update the contract when connectors change. Manual review may suffice at low volume. Automating a poorly defined field multiplies errors rather than resolving them.
Sources and limitations
Documentary review: . Content type: Documentation-based guide with original exercise.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- ifempty, omit and the erase keywordhelp.make.com
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
MakeAffiliate linkThe labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.