Okay, I think I see what’s happening here. n8n queries new SeaTable rows using timestamps in the GMT timezone (which is also the time zone SeaTable returns timestamps in). However, at least on the SeaTable cloud version it seems SeaTable requires a local timestamp in the query (but returns a GMT/UTC timestamp in the result).
I am not sure if it’s the same time zone for all SeaTable instances (if so, a fix would be easy to implement) or if this is a setting somewhere. I’ve posted on their forum to find out more and will keep you updated 