N8n integration on version 1.99.1 not working

[dakoller]

Your Setup:

• SeaTable Cloud

Describe the Problem/Error/Question:

Same issue as in All n8n integrations failing as of today - #3 by lcx_at .

Issues: * There was a problem loading the parameter options from server: “The resource you are requesting could not be found”

However it seems that in the previous case the issue was on seatable side.

Error Messages:

If there are any error messages shown in the browser console, please include them for better readability by wrapping them in a code block.

Example of a code block for error messages

[cdb]

Please provide more information about your setup.

• SeaTable Cloud or SeaTable Server?
• n8n Cloud or Self-hosted?

I tested version 1.99.1 with the “Get Many” endpoint and it worked like a charm.
Please use api.seatable.com to get more information what is wrong.

[lcx_at]

did you check your nginx config as described in my Post? I was missing just that.

    location /api-gateway/ {
      add_header Access-Control-Allow-Origin *;
      add_header Access-Control-Allow-Methods GET,POST,PUT,DELETE,OPTIONS;
      add_header Access-Control-Allow-Headers "deviceType,token, authorization, content-type";
      if ($request_method = 'OPTIONS') {
          add_header Access-Control-Allow-Origin *;
          add_header Access-Control-Allow-Methods GET,POST,PUT,DELETE,OPTIONS;
          add_header Access-Control-Allow-Headers "deviceType,token, authorization, content-type";
          return 204;
      }
      proxy_pass         http://127.0.0.1:7780/;
      proxy_redirect     off;
      proxy_set_header   Host              $http_host;
      proxy_set_header   X-Real-IP         $remote_addr;
      proxy_set_header   X-Forwarded-For   $proxy_add_x_forwarded_for;
      proxy_set_header   X-Forwarded-Host  $server_name;
      proxy_set_header   X-Forwarded-Proto $scheme;
      access_log         /opt/nginx-logs/api-gateway.access.log seatableformat;
      error_log          /opt/nginx-logs/api-gateway.error.log;
  }

[dakoller]

Hi @cdb !

1. I use the cloud.seatable.io version ( more specifically Log in - SeaTable Cloud in case you can see it ).

2. n8n is self hosted and on the current version 1.100.1 now.

3. I see also in the logs “404 - “This endpoint is deprecated. Please migrate to the API Gateway: …””

Best regards,

Daniel

[dakoller]

@lcx_at I am using the prepackaged version of n8n, which is deployable using dokploy, which means I am limited to the environment settings, which I can do via docker-compose.

The dokploy version of the docker-compose based n8n-deployment is available at templates/blueprints/n8n/docker-compose.yml at 1d567e4df94934bebadb999c8fb7ebdbea09402d · Dokploy/templates · GitHub .

[lcx_at]

oh, ok, I thought self hosted seatable.
I see the problem now, the blueprint has this n8n version: image: docker.n8n.io/n8nio/n8n:1.83.2 That’s a bit outdated. The current stable version is 1.100.1 can You upgrade n8n to that version?
Or just use :latest which contains the latest stable version.
Another option is to use the n8n seatable community node instead but upgrading n8n is highly recommended.
Was planing to write a self hosted howto on how to set up n8n including backups, I should really get to that.

[SebSa]

Following worked for me.

1. Update latest Version
2. Create new Seatable Node

The old node had the issue to succesfully connect but does not fetch
New node runs like without a flaw

[dakoller]

Recreating the nodes helped.

Only since the new nodes are used the “Get Many [Rows]” does not deliver the Seatable Row-id anymore. :-/

[cdb]

Set the option Simplify to false, then you also receive the _id of the row.