How to Fix Wix REST API Date Fields in Make.com (Undocumented Patch Method)
If you've ever updated a date field in Wix via REST API only to find it mysteriously corrupted with validation warnings, you're not alone. The documentation doesn't mention this critical formatting requirement that makes all the difference between broken dates and perfectly functioning ones.
The Hidden Date Field Problem
When Wix introduced their PATCH function for REST API, it solved a major pain point - the ability to update single fields without retrieving and resending all collection data. But there's an undocumented quirk with date fields that can silently corrupt your data.
At first glance, everything appears to work. Your Make.com scenario runs without errors, the date appears updated in your Wix collection, and no warnings appear in your automation logs. But behind the scenes, Wix marks these dates as invalid with a yellow triangle warning icon.
The silent corruption: These improperly formatted dates will still display, but they won't function correctly in date-based queries, sorting, or calculations. Your workflows may work today but fail unpredictably tomorrow when relying on these corrupted date values.
Standard vs. Correct Approach
The Wix documentation shows updating fields with direct values - for dates, this would be an ISO string like "2023-11-15T12:00:00.000Z". This appears to work initially but causes the hidden validation issue.
The correct approach requires wrapping your date string in an object structure. Instead of sending the date directly as the field value, you send an object with the date as a property:
{ "last_push_live": { "value": "2023-11-15T12:00:00.000Z" } } This matches Wix's internal date storage format and prevents the validation warning while ensuring full date functionality.
Why Wix Dates Behave This Way
Wix stores date fields internally as objects containing ISO string representations. When you inspect the raw data from a Wix collection, properly formatted dates appear like this:
"last_push_live": { "$date": "2023-11-15T12:00:00.000Z" } When you update a date field with just the string value, Wix accepts it but flags it as invalid because the internal structure doesn't match what the system expects. The object wrapper maintains this expected structure.
Technical insight: This behavior stems from Wix's MongoDB backend, which stores dates in this specific object format. The REST API expects dates to maintain this structure during updates, even though the documentation doesn't mention this requirement.
Implementing the Fix in Make.com
In your Make.com scenario, when configuring the Wix REST API module to update a date field, you'll need to structure your data differently than the documentation suggests.
Instead of setting the field value directly to your date string, create an object with a "value" property containing your date:
- In your Make.com scenario, add a "Set Multiple Fields" action in the Wix module
- For date fields, set the value to an object like:
{"value": "2023-11-15T12:00:00.000Z"} - For non-date fields, continue using direct values as normal
- Run a test scenario to verify the date updates without validation warnings
This small structural change makes all the difference in maintaining data integrity while keeping your automation running smoothly.
Testing Your Date Updates
After implementing the object wrapper for your date fields, you'll want to verify everything works correctly. Here's how to test your updates:
First, check the Wix collection editor directly. A properly formatted date will show without the yellow warning triangle (visible at 2:10 in the video tutorial). Then inspect the raw data through the Wix API or Data API to confirm the date appears as an object with the $date property.
Finally, test any downstream functionality that relies on these date fields - sorting, filtering, date math, or time-based triggers. These should all work as expected once your dates are properly formatted.
Watch the Full Tutorial
See the complete walkthrough of this Wix date field fix in action, including before/after examples of the corrupted vs. properly formatted dates (demonstrated at 1:45 in the video).
Key Takeaways
Properly formatting date fields in your Wix REST API calls prevents hidden data corruption and ensures reliable date functionality throughout your application.
In summary: Always wrap Wix date field updates in an object structure with a "value" property containing your ISO date string. This matches Wix's internal storage format and prevents validation issues while maintaining full date functionality.
Frequently Asked Questions
Common questions about this topic
Wix stores date fields internally as objects with ISO string representations. When you update them directly with a string value, the system flags it as invalid format even though it appears to work initially.
This causes the yellow triangle warning icon and prevents proper date field functionality in queries, sorting, and calculations. The validation error indicates the date isn't stored in Wix's expected internal format.
- Key symptom: Yellow triangle icon in collection editor
- Root cause: Mismatch between direct string and expected object format
- Impact: Dates may fail in queries and time-based operations
The proper format wraps your date string in an object with a "value" property. Instead of sending just the ISO string, you send an object containing that string.
For example, to update a "last_updated" field, your PATCH data should look like: {"last_updated": {"value": "2023-11-15T12:00:00.000Z"}}. This matches Wix's internal storage structure.
- Required structure: Field name → object with "value" property
- Date format: ISO 8601 string (YYYY-MM-DDTHH:MM:SS.sssZ)
- Verification: No warning triangle in collection editor
No, this specific object format is only required for date fields. Other field types like text, numbers, and booleans should be updated with direct values as shown in the standard Wix REST API documentation.
The object wrapper is specifically needed for dates due to Wix's internal MongoDB-based storage format. Using this structure for non-date fields may cause unexpected behavior or errors.
- Date fields only: Requires special object wrapper
- Other fields: Use direct values per documentation
- Exception: Some complex field types may need similar treatment
The most visible indicator is the yellow warning triangle that appears next to date values in your Wix collection editor. This icon signals a validation error on the field.
You can also check the raw data output from your API calls. Properly formatted dates will appear as objects with $date properties, while corrupted dates will show as plain strings.
- Visual cue: Yellow triangle in collection editor
- API check: Corrupted dates show as strings, not objects
- Functional test: Date-based queries may fail
Yes, this solution applies to any platform making REST API calls to Wix, including Make.com, n8n, custom code, or other automation tools. The key is sending the date in the correct object structure.
The implementation details may vary slightly between platforms (how you construct the object in each tool's interface), but the fundamental requirement of wrapping dates in an object remains the same.
- Platform-agnostic: Works with any REST API client
- Make.com: Use "Set Multiple Fields" with object values
- n8n: Structure your JSON payload accordingly
Corrupted date fields may display incorrectly, fail in date-based queries, cause errors in downstream automations, and prevent proper sorting/filtering. The issues often appear intermittently.
Over time, these invalid dates can break time-sensitive business processes that rely on accurate date calculations and comparisons, leading to data integrity problems and workflow failures.
- Immediate: Validation warnings but basic display works
- Mid-term: Failed queries and sorting operations
- Long-term: Broken time-based business logic
Yes, you can update multiple date fields in a single PATCH request by including each date field with its own object wrapper. The format would be an object containing all your date fields.
For example: {"date_field1": {"value": "date1"}, "date_field2": {"value": "date2"}}. This maintains proper formatting for all date fields while minimizing API calls.
- Multiple fields: Include all in single PATCH
- Mixed types: Combine date and non-date fields
- Efficiency: Reduces API calls versus individual updates
GrowwStacks helps businesses implement automation workflows, AI integrations, and scalable systems tailored to their operations. We specialize in fixing exactly these kinds of undocumented API quirks that can derail your automations.
Whether you need a custom workflow, AI automation, or a full multi-platform automation system, the GrowwStacks team can design, build, and deploy a solution that fits your exact requirements while avoiding pitfalls like the Wix date field issue.
- Custom automation: Workflows built for your business needs
- Platform expertise: Deep knowledge of Make.com, n8n, and API quirks
- Free consultation: Discuss your automation goals with our team
Stop Fighting Wix API Quirks - Let Us Handle Your Automation
Hidden issues like the date field problem can waste hours of debugging time and compromise your data integrity. Our team lives in these APIs daily and knows all the undocumented requirements that can make or break your automations.