# Postgresql Insert error parsing ISO format string **URL:** \ **Category:** Questions\ **Tags:** postgres, date-time\ **Created:** [September 19, 2025, 1:48am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598 "2025-09-19T01:48:50Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![DragonPow](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/dragonpow/32/121200_2.png) [@DragonPow](https://community.n8n.io/u/DragonPow)\ **Post date:** [September 19, 2025, 1:48am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/1 "2025-09-19T01:48:50Z")
I using Postgresql Insert node, but it error when column type is `timestamp` I have the input date in ISO 8601 date string format and I keep getting an error. ## What is the error message (if any)? Input of Insert node ![image](https://europe1.discourse-cdn.com/n8n/original/3X/0/1/0139bfd109a4b7d6e89240e87c7dcc4ad1be32c8.png) Output of Insert node ![image](https://europe1.discourse-cdn.com/n8n/original/3X/b/1/b10de5d115c9fa0231b063d3eb338a2dce359dc9.png) ## Please share your workflow ```auto (Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.) ``` ## Share the output returned by the last node Error Message: parsing as type timestamp: unexpected separator ‘"’ for field Year Wanted: [Year Month Day Era Hour Minute Second Nanos Meridian TZHour TZMinute TZSecond] Already found in input: I expected to successful insert base this document [Postgres node common issues | n8n Docs](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.postgres/common-issues/) ## Information on your n8n setup - **n8n version:** 1.111.0 - **Database (default: SQLite): Postgresql** - **n8n EXECUTIONS\_PROCESS setting (default: own, main):** - **Running n8n via (Docker, npm, n8n cloud, desktop app): Docker** - **Operating system: Ubuntu 20.04** ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [September 19, 2025, 2:26am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/2 "2025-09-19T02:26:35Z")
Hey @DragonPow hope all is good. Took your input data and populated my db with it. My DB: ![image](https://europe1.discourse-cdn.com/n8n/original/3X/e/2/e2a34fd39875cebf4fd52ee762e71f83e9415e45.png) Workflow: Result: ![image](https://europe1.discourse-cdn.com/n8n/original/3X/e/8/e8c800ef6b92437e8c9472e33dce7fd34321a86d.png) ---
**Author:** ![DragonPow](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/dragonpow/32/121200_2.png) [@DragonPow](https://community.n8n.io/u/DragonPow)\ **Post date:** [September 19, 2025, 2:54am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/3 "2025-09-19T02:54:32Z")
I think maybe wrong with n8n configuration, it fail when parse from input of n8n, not in DB query Insert ![image](https://europe1.discourse-cdn.com/n8n/original/3X/9/b/9b9dadcb29c3cca0be10c7dfa53e8033b3b4a277.png) ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [September 19, 2025, 2:58am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/4 "2025-09-19T02:58:03Z")
> [@DragonPow](#): > > I think maybe wrong with n8n configuration it is possible, want to share some of it? ---
**Author:** ![DragonPow](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/dragonpow/32/121200_2.png) [@DragonPow](https://community.n8n.io/u/DragonPow)\ **Post date:** [September 19, 2025, 3:14am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/5 "2025-09-19T03:14:56Z")
This is my input ![image](https://europe1.discourse-cdn.com/n8n/original/3X/2/e/2e06c482e916d1c8e267374eaab7b9cf25a3c9c5.png) ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [September 19, 2025, 4:06am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/6 "2025-09-19T04:06:43Z")
Can you copy and paste your workflow here? ---
**Author:** ![DragonPow](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/dragonpow/32/121200_2.png) [@DragonPow](https://community.n8n.io/u/DragonPow)\ **Post date:** [September 19, 2025, 4:18am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/7 "2025-09-19T04:18:32Z")
here ![image](https://europe1.discourse-cdn.com/n8n/original/3X/f/9/f9c2be46fa5e895228fb13c05a2c5c61a66a18ad.png) ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [September 19, 2025, 4:21am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/8 "2025-09-19T04:21:42Z")
First thing that jumped out - is you have all the fields on the left and in the table named the same. If this is actually the case in your actual workflow - you could just use automatic mapping. Let me now take alook at the rest. ---
**Author:** ![DragonPow](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/dragonpow/32/121200_2.png) [@DragonPow](https://community.n8n.io/u/DragonPow)\ **Post date:** [September 19, 2025, 4:31am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/9 "2025-09-19T04:31:06Z")
this problem still occurred with node Postgresql Update, so i want to find problem to fix it instead of using automate mapping ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [September 19, 2025, 4:37am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/10 "2025-09-19T04:37:14Z")
yeah, no issues with your workflow on my side ![image](https://europe1.discourse-cdn.com/n8n/original/3X/2/5/25ebddb656b804297ce6246ab117f62e3e441455.png) ![image](https://europe1.discourse-cdn.com/n8n/original/3X/0/6/0670c90604389ce2c0548308a7933b9254723bfc.png) ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [September 19, 2025, 4:45am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/11 "2025-09-19T04:45:04Z")
Maybe try `{{ $json.thoi_gian_bd.toDateTime() }}` `{{ $json.thoi_gian_kt.toDateTime() }}` ---
**Author:** ![DragonPow](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/dragonpow/32/121200_2.png) [@DragonPow](https://community.n8n.io/u/DragonPow)\ **Post date:** [September 19, 2025, 7:10am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/12 "2025-09-19T07:10:34Z")
also error with fixed value ![image](https://europe1.discourse-cdn.com/n8n/original/3X/c/b/cb7930554b80777d531fa60a33e52511d277fe08.png) ```sql CREATE TABLE public.test ( id serial PRIMARY KEY, thoi_gian_bd timestamp without time zone, thoi_gian_kt timestamp without time zone ); ``` ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [September 19, 2025, 2:31pm UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/13 "2025-09-19T14:31:38Z")
Let’s compare things: ```auto SELECT version(); ``` > PostgreSQL 16.10 on x86\_64-pc-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit ```auto SELECT '2025-09-18T16:00:00.000+07:00'::timestamptz; ``` > 2025-09-18 09:00:00+00 ```auto SHOW DateStyle; ``` > ISO, MDY ```auto SHOW lc_time; ``` > en\_US.utf8 ```auto SHOW TimeZone; ``` > UTC ```auto SHOW client_encoding; ``` > UTF8 ---
**Author:** ![DragonPow](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/dragonpow/32/121200_2.png) [@DragonPow](https://community.n8n.io/u/DragonPow)\ **Post date:** [September 22, 2025, 1:41am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/14 "2025-09-22T01:41:53Z")
oh I see I using cockroachDB as an instance of Postgresql database, maybe problem exists here ---
**Author:** ![jabbson](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jabbson/32/87328_2.png) [@jabbson](https://community.n8n.io/u/jabbson)\ **Post date:** [September 22, 2025, 1:48am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/15 "2025-09-22T01:48:41Z")
This definitely could be the reason. While CockroachDB is Postgres-compatible, it is not Postgres. Its timestamp parsing is implemented in Go and is **stricter**. That exact error (“unexpected separator ‘"’ for field Year … wanted: [Year Month Day …]”) is Cockroach’s Go-style parser complaining that the value it’s trying to parse **starts with a double quote**. You may have to switch to using execute statement operation and try to cast required types explicitly. ---
**Author:** ![DragonPow](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/dragonpow/32/121200_2.png) [@DragonPow](https://community.n8n.io/u/DragonPow)\ **Post date:** [September 22, 2025, 1:50am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/16 "2025-09-22T01:50:39Z")
thank for your support ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [September 29, 2025, 1:51am UTC](https://community.n8n.io/t/postgresql-insert-error-parsing-iso-format-string/190598/17 "2025-09-29T01:51:09Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.