# Workflow date format **URL:** \ **Category:** Ask for Help\ **Created:** [June 28, 2024, 11:26am UTC](https://community.noloco.io/t/workflow-date-format/894 "2024-06-28T11:26:12Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![garyGHL](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/garyghl/32/555_2.png) [@garyGHL](https://community.noloco.io/u/garyGHL)\ **Post date:** [June 28, 2024, 11:26am UTC](https://community.noloco.io/t/workflow-date-format/894/1 "2024-06-28T11:26:12Z")
Hello, we are UK based so date formats are 28/06/2024, the front end app itself does display this correctly but the database table displays 06/28/2024, this then causes the workflows to also display 06/28/2024 when using any dates in push notifications, emails & comments. Not a massive issue but is there setting I’ve missed to resolve this at all? ---
**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\ **Post date:** [June 28, 2024, 12:34pm UTC](https://community.noloco.io/t/workflow-date-format/894/2 "2024-06-28T12:34:29Z")
> [@garyGHL](#): > > Not a massive issue but is there setting I’ve missed to resolve this at all? There’s not no, if you want to use dates in a workflow/automation you should use a formula field to format the date the way you want it In your app, we can tell where you’re located, that’s not possible from workflows. In the future we might introduce an ‘App locale’ setting, but it’s not something we support right now ---
**Author:** ![garyGHL](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/garyghl/32/555_2.png) [@garyGHL](https://community.noloco.io/u/garyGHL)\ **Post date:** [June 9, 2025, 11:03am UTC](https://community.noloco.io/t/workflow-date-format/894/3 "2025-06-09T11:03:28Z")
Just revisited this as its now throwing random dates too. I just created this record front end: ![image](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/2X/a/a1121693cdf7c23bf28a8867abf6ba2df3a22448.png) This is the email we received via workflow: ![image](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/2X/5/56f45e6fa6b7a29fbd8db843e08c864c9125098c.png) Date format is different from the table and hour is -1. If the user doesnt select a time it defaults to this: ![image](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/2X/e/e2c0691ffaf00f87d5020ec9cd8a35357b9619ac.png) ---
**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\ **Post date:** [June 9, 2025, 12:00pm UTC](https://community.noloco.io/t/workflow-date-format/894/4 "2025-06-09T12:00:01Z")
Hey @garyGHL , workflows will format your dates in US format (mm/dd/yyyy) and in UTC. UK, where you’re based is currently GMT+1 which is one hour ahead of UTC, which is why you’re seeing the times “wrong” If you want to use them exactly as that in your workflows, you’ll need to either specify the timezone in your email, or use a formula to convert it to your timezone (or the one you need) ---
**Author:** ![garyGHL](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/garyghl/32/555_2.png) [@garyGHL](https://community.noloco.io/u/garyGHL)\ **Post date:** [July 1, 2025, 10:41am UTC](https://community.noloco.io/t/workflow-date-format/894/5 "2025-07-01T10:41:50Z")
Hi @darragh , following up on this one if I may, the date format is correct in the table as below. Do you know how I would specify the timezone in the workflow email? ![image](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/2X/9/9637cfdcff777cc754aa9198a2dc4200cdc96a91.png) ![image](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/2X/b/b30c49332c6e9ac5a3643515b0d2c309b007ac50.png) ---
**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\ **Post date:** [July 1, 2025, 11:26am UTC](https://community.noloco.io/t/workflow-date-format/894/6 "2025-07-01T11:26:01Z")
@garyGHL - you’ll have to use a formula to format it correctly for your workflow \ ---
**Author:** ![garyGHL](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/garyghl/32/555_2.png) [@garyGHL](https://community.noloco.io/u/garyGHL)\ **Post date:** [July 1, 2025, 11:54am UTC](https://community.noloco.io/t/workflow-date-format/894/7 "2025-07-01T11:54:01Z")
Didn’t know that was a thing. I tried this in the workflow email setting but it outputs the code rather than date. Did I misunderstand what you meant 🙂 You have an appointment scheduled for **TEXT(created at, “DD/MM/YYYY”)** **created at** is the field in question that shows 01/07/25 correctly in the table. ---
**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\ **Post date:** [July 1, 2025, 12:37pm UTC](https://community.noloco.io/t/workflow-date-format/894/8 "2025-07-01T12:37:59Z")
Sorry if I wasn’t clear @garyGHL . You’ll have to add a new [Formula Field](https://guides.noloco.io/data/collections/formulas) to your table, with the desired format, and then use that in your email. ---
**Author:** ![garyGHL](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/garyghl/32/555_2.png) [@garyGHL](https://community.noloco.io/u/garyGHL)\ **Post date:** [July 1, 2025, 12:54pm UTC](https://community.noloco.io/t/workflow-date-format/894/9 "2025-07-01T12:54:36Z")
No worries @darragh . Just so I understand for future purposes, the date field in the table displays correctly at the moment. So I need to create another formula field based on this field to format it to UK (which it already is)? Current field = 01/07/2025 Formula field = 01/07/2025 Then use the formula field in the workflow email. Am I correct in thinking the real format under the current field is (mm/dd/yyyy) but for display purposes it outputs it the regional settings? ---
**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\ **Post date:** [July 1, 2025, 1:28pm UTC](https://community.noloco.io/t/workflow-date-format/894/10 "2025-07-01T13:28:43Z")
> [@garyGHL](#): > > Just so I understand for future purposes, the date field in the table displays correctly at the moment. So I need to create another formula field based on this field to format it to UK (which it already is)? DateTime fields in Noloco are represented in _local_ time and formatting, i.e. time time of your computer which is why they display ‘correctly’. When the email is sent, it’s sent from the API, which doesn’t know what Timezone you are in, so it’s sent in UTC and default (US) formatting. So if you have a text-formula of the date field, which will display as text, regardless of where you are in the world, it will always be correct for your use-case. You can read more about our DateTime fields here: [Dates & Time Zones | Noloco](https://guides.noloco.io/field-formatting/dates-and-time-zones#date-and-time) We’re hoping to have better ways to do this in the future. ---
**Author:** ![garyGHL](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/garyghl/32/555_2.png) [@garyGHL](https://community.noloco.io/u/garyGHL)\ **Post date:** [July 1, 2025, 1:50pm UTC](https://community.noloco.io/t/workflow-date-format/894/11 "2025-07-01T13:50:19Z")
> [@garyGHL](#): > > TEXT( **created at** , “DD/MM/YYYY”) Great, go that now. I’ll apply to the smaller examples, we do have tables with lots of date fields so may leave those until a time it becomes imperative. Thank you