EDIT: Ok could be that my seatable database migrations failed, as I see different variables returned when I create a new base… Will inquire and report back
EDIT2: Nope, curiously I get “_ctime”: “2023-04-21T17:00:19Z” when I call the column _ctime or don’t have the column at all in seatable, yet when I call it sth else it returns null (for example called “timestamp”)…
EDIT 3: When the seatable credential timezone is empty AND my workflow timezone is set to Azores (GMT-1) instead of Berlin (GMT+1) it triggers. Seatable docker-compose TIME_ZONE=Etc/UTC
When I rename the _ctime column to timestamp it still triggers, but then shows null as the value in the execution data.
EDIT 4: Ok probably just use Webhooks instead like referenced here
I have set it aside using a workaround. Just today I wanted to finally get it working again, but I can’t seem to. Tried setting my Seatable self-hosted version to TIME_ZONE=Etc/UTC and also tried TIME_ZONE=Europe/Berlin. I tried setting my n8n seatable credentials to Europe/Berlin.
This is really frustrating as I have the feeling it should be sth super simple, but somehow I can’t see where I’m going wrong…
When just hitting Execute Workflow the timestamp of 2022-11-20 00:08:53 displayed in Seatable does not return in n8n but shows null, only if I query that table via the node do I get that value as 2022-11-19T23:08:53.936+00:00
My workflow timezone is set to Standard / Berlin.
Any thoughts / ideas what I do wrong or what I could check, try, etc @MutedJam ?
Seatable self-hosted Developer Edition: 3.5.0
N8N self-hosted: 0.222.3