n8n turned your date into yesterday for a reason
A customer selects 14 May as a project start date. The form looks right, the n8n workflow runs, and the CRM receives 13 May. For a Dubai, UAE or UK service business, that can put an appointment, deadline or onboarding task against the wrong day before anyone notices.

The tempting fix is to add or subtract hours until the display looks sensible. That may hide the immediate symptom, but it does not settle what the value is meant to represent. Agree what the date means before agreeing how it is formatted.
Two values that look similar but behave differently
A date-only value and a timestamp are different bits of information. Treating them as interchangeable is the usual cause of the consistent one-day discrepancy.
| Value type | What it means | Example | What n8n should preserve |
|---|---|---|---|
| Calendar date | A named day, without a time or location | 2025-05-14 for a project start | The same date text, unless a business rule deliberately changes it |
| Timestamp | A precise moment in time | 2025-05-14T09:00:00+04:00 for a meeting | The instant, with its source timezone understood |
| Local date and time | A time intended in a particular place | 2025-05-14 09:00 in Dubai | The local time and the named timezone used to interpret it |
A calendar date does not need converting through UTC merely because it passes through an automation. There is no instant to convert. If 14 May means the contractual or operational start day, turning it into midnight in one timezone and rendering it in another has quietly changed the information.
The direct answer: why n8n shows the previous day
n8n can show a date as the previous day when a date-only value is parsed as midnight in one timezone and then formatted in another timezone behind it. The safe approach is to identify whether the source is a calendar date or a timestamp, preserve date-only values as dates where appropriate, and explicitly parse timestamps using the known format and timezone before sending them onward.
n8n documents that date values pass between nodes as strings, and recommends explicit Luxon parsing where the format and timezone behaviour need to be controlled. Its date and time handling guidance is worth reading before adding a convenient-looking offset expression.
Inspect the raw value before changing the workflow
Start with the value as it arrived, not the value shown in a later app. Check the execution data from the node that first receives the field and note the exact characters.
- 2025-05-14 is normally a date-only string.
- 2025-05-14T00:00:00Z is midnight at a UTC instant.
- 2025-05-14T00:00:00+04:00 is midnight with an explicit offset.
- 14/05/2025 may be a date, but its format needs agreeing before parsing.
This dull detail matters. A form field may send 2025-05-14, while a mapping node or destination API turns it into a JavaScript-style date object assumption. By the time somebody sees 13 May in a CRM, the original meaning can be several nodes behind them.
Comparison: preserve a date or convert an instant?
Keep a calendar date as a date string
Use this route for project start dates, due dates, birthdays, leave dates and other values where the named day matters more than the exact moment. Define an accepted format, validate it, and send the same date-only representation to systems that support date fields.
Illustrative example: a customer chooses 14 May for a website content handover. The workflow creates tasks for that day. It should not manufacture 00:00 UTC, because a user viewing the resulting record in a western timezone may see 13 May.
Convert a timestamp with an explicit timezone contract
Use this route for booked calls, clinic appointments, delivery windows and anything that happens at a particular time. Record the source format, source timezone, target timezone, and required output format. Then parse and format deliberately rather than relying on node defaults or server settings.
If the workflow needs broader review across forms, CRM records and follow-up actions, business automation support for operational workflow checks is a sensible place to scope it.
Write the conversion contract down
A small note beside the workflow can prevent a lot of later guesswork. It should answer four questions:
- What does this field represent: date, timestamp, or local date and time?
- What exact format does the sender provide?
- Which timezone applies when a time has no offset?
- What format and timezone must the receiving system store or display?
For example: project_start_date is a calendar date supplied as YYYY-MM-DD and must remain a date-only value in the CRM. That is a complete contract. Compare it with: consultation_start is supplied as a Dubai local timestamp and must be stored as an ISO timestamp, then displayed in the recipient’s selected timezone. Different field, different job.
Test the dates that expose a bad assumption
Do not test only a comfortable weekday at 10:00. Use a small controlled set that includes midnight, a date near month end, and daylight-saving boundaries where the relevant locations observe them. Dubai does not use daylight saving time, but a workflow involving UK contacts, UK-hosted systems or a UK CRM user may still cross that boundary.
Check the destination record itself, not merely the n8n preview. A contact form success message proves only that the form submitted. It does not prove that the CRM stored the date with the intended meaning.
Keep this separate from a schedule problem
A workflow firing at 09:00 instead of the intended local hour is a scheduling issue. A customer-entered 14 May becoming 13 May is a data-meaning issue. They can both involve timezones, but they need different diagnosis. If the trigger timing is wrong rather than the field value, see the separate guide on n8n Schedule Trigger timezone checks.
There is one operational consequence worth taking seriously: a wrong date can release a task early, start an onboarding sequence on the wrong day, or leave staff chasing a customer before their agreed start date. Where a meaningful customer record changes during a process, it may be worth designing a review pause rather than letting queued actions carry on regardless. See how to pause onboarding when customer details change for that adjacent workflow decision.
Do not repair a date bug with a permanent offset
Adding 24 hours may make one example look correct and damage another. It is especially risky when the source sometimes contains a true timestamp and sometimes a date-only field, or when the workflow serves people across Dubai and the UK.
Make the narrow correction: preserve calendar dates as dates, parse true timestamps from a declared source format and timezone, then test the boundary cases in the real destination.
If one field is consistently landing on the wrong day, Bring one source date and its incorrect destination value for a conversion-contract review.