SeaTable and make.com have a bit of a history. The first version of a SeaTable make.com app was developed by make.com and included only some of the desired features.
Since I wasn’t given access to this app, I created my own. For SeaTable Rework, an invitation link for make.com was needed.
Shortly thereafter, I was granted permission to edit the official SeaTable app and added the missing features to the official app.
Since then, SeaTable Rework is no longer needed. The following only concerns the official SeaTable make.com app.
Which Version Are You Using
You can easily find this out in the scenario editor of make via mouse hover. It should say “SeaTable” and not “SeaTable Rework”.
After updating SeaTable to version 5.3, make.com scenarios that used the SeaTable app stopped working. I would like to sincerely apologize for this.
The problem arose due to make.com’s development process. As a developer, in addition to the official app that everyone can use, I have access to a “Custom App”. This always contains my latest code. It looks like this:
I had already made the necessary changes for 5.3, migrated all endpoints from dtable-db and dtable-server to the API Gateway, and tested everything. However, these changes did not make it into the code. I had committed my changes via Visual Studio, but must have missed the error message stating that only make.com admins can submit commits this way.
Last night, my changes have been accepted and the Make.com scenarios should all be working again. If not, please try recreating the individual node, and if that doesn’t help, post here in the forum.
Hi and thanks @cdb for the info. We had few issues yesterday, but lots of issues today. We only use the Seatable [verified] app.
Right now, at least these 3 modules/endpoints are not working (might be more, haven’t tried them all)
Create a row [Cannot GET /dtable-server/api/v1/dtables/XXXXXXXXXX/columns/] Search rows [Cannot POST /dtable-db/api/v1/query/XXXXXXX/] Update row [Cannot PUT /api-gateway/api/v2/dtables/XXXXXXXX/rows/]
EDIT: All modules affected. The issue is with the OAuth connection for existing connections.
Plus, the “Create a row” has a “(Deprecated)” suffix. Replacing this with a new “Create a row” module does not help.
We’ve had the exact same issues in our seatable modules in make. adding a new connection from make to seatable with a fresh API token & changing all the modules to this new connection did the trick for us. Hope that helps for you as well!
Oh no, that sounds terrible. We have lots of tables in prod and even more Make scenarios. As I interpret @cdb :s information, it should not be needed to recreate all the connections?
Far from ideal for sure! I tried simply recreating the individual nodes which ran into an error as described by @cdb but that simply led to the same issues unfortunately.
I have noticed 2 changes that need to be made: 1. The old connection to SeaTable doesn’t work and needs to be replaced. Then it connects. 2. Redo the modules to remove “Rework” and only use the official. 1) is easy, but 2) is a major pain.
Thanks for sharing your experience. make.com support told me, that the individual modules update themself to the latest code version and there would be no need to update. It seems this is not the case.
For sure, if you use an old module with “deprecated” in the name, then you have to replace it.
I have just been through one instance and replaced the connection and any rework modules and everything works now.
Note: Sometimes looking for “rework” in the module name didn’t work because many of our modules have been renamed to better recognise what they are for. Often, the only way to tell was to see if the new connection popped up in the list of possible connections. If it didn’t, it must have been the “rework” module, as the new connection is only for the “verified” modules.
I am confussed. Wehave self hosting version of Seatable, not updated yet to lates version, and make integration not working even if I delete a connection, recreate api. Do we have to install latest version of Seatable before?
@cdb: Now that all my workflows are based on “SeaTable Rework”, I wonder if this module will still be maintained - and if so, for how much longer?
A mixed operation between “Rework” and “Verified” seems to be possible as an interim solution. In our case, initially only all “Search Rows / with SQL” calls had to be replaced by SeaTable Verified. We also used new API tokens and Make.com connections for this - given the time pressure, we did not check whether this was absolutely necessary.
Switching from “Rework” to “Verified” means manually replacing and customizing every single SeaTable call in Make.com. This is a very time-consuming and error-prone task and requires all Make.com scenarios to be fully tested - during live operation. Great!
Dear @make-webdev, I can not reproduce your problem.
I tested the “Watch New Rows” with a SeaTable v5.2. and a SeaTable 5.3. There were no errors.
Please recreate the module and use a new connection. Also make sure to use “verified”. Then it will work.
