I don’t understand why this can’t work. If you use self-hosted n8n, just make sure n8n use the same timezone as the SeaTable server.
n8n uses the UTC timezone for database queries and that’s currently hard coded. So changing the n8n time zone would not help here.
One of the possible approaches I could think of was allowing users to configure their SeaTable timezone along with the SeaTable credentials. Obviously, it would be much more convenient if users wouldn’t have to do that.
But assuming that’s not possible: How would a user know the SeaTable server time zone if where they do not have access to the respective docker compose file or environment variables? Or where SeaTable cloud is being used?
Or would correctly querying rows by their creation date always require reading the TIME_ZONE environment variable on the SeaTable server?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
