# N8n action node type changed

**URL:** <https://forum.seatable.com/t/n8n-action-node-type-changed/4961>\
**Category:** Integrations\
**Tags:** bug, n8n\
**Created:** [July 25, 2024, 3:15pm UTC](https://forum.seatable.com/t/n8n-action-node-type-changed/4961 "2024-07-25T15:15:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bha](https://forum.seatable.com/user_avatar/forum.seatable.com/bha/32/4702_2.png) [@bha](https://forum.seatable.com/u/bha)\
**Post date:** [July 25, 2024, 3:15pm UTC](https://forum.seatable.com/t/n8n-action-node-type-changed/4961/1 "2024-07-25T15:15:12Z")

</div>

Hi,  
I just updated my n8n-nodes-seatable from 1.5.2 (pretty old I must admit !) to 1.6.3 and I can’t activate any of my workflows, because the seatable action nodes type changed from `n8n-nodes-seatable.seatable` to `n8n-nodes-seatable.seaTable` (the type of the trigger nodes remains n8n-nodes-seatable.seaTableTrigger so they don’t cause any problem)…

The correction is pretty straight-forward : copying all the workflow in a text editor, replacing `n8n-nodes-seatable.seatable` by `n8n-nodes-seatable.seaTable` and pasting the result back in n8n, but it will take me some time and I’m a bit surprised: I didn’t find anything about that on the forum, did I miss the info ? Am I the only one having this problem ? And the vexing question for the SeaTable team: are we talking about backwards compatibility ?

Don’t get me wrong, I still love you all and I’m still a big fan of SeaTable ❤

---

<div class="post-metadata">

**Author:** ![cdb](https://forum.seatable.com/user_avatar/forum.seatable.com/cdb/32/7_2.png) [@cdb](https://forum.seatable.com/u/cdb)\
**Post date:** [July 25, 2024, 7:59pm UTC](https://forum.seatable.com/t/n8n-action-node-type-changed/4961/2 "2024-07-25T19:59:42Z")

</div>

Thanks for your hint. I am surprised and sorry at the same time.  
The change you mentioned happened with version 1.5.1 ([version 1.5.1 including big data · seatable/n8n-node@65fc840 · GitHub](https://github.com/seatable/n8n-node/commit/65fc840c371f39583af27d625fa2794aebf6b785)) and should be no problem.

The n8n developers asked me to do this change to fullfill their naming policies. Still I thought this should be no problem and automatically updated automatically as soon as you update the community node.

Regarding your complaints: we do our best to develop and improve SeaTable and the complete eco-system without friction for any user. Sometimes this works not as expected and we are sorry about that.

---

<div class="post-metadata">

**Author:** ![bha](https://forum.seatable.com/user_avatar/forum.seatable.com/bha/32/4702_2.png) [@bha](https://forum.seatable.com/u/bha)\
**Post date:** [July 27, 2024, 3:46pm UTC](https://forum.seatable.com/t/n8n-action-node-type-changed/4961/3 "2024-07-27T15:46:27Z")

</div>

Hi Christoph,  
Thanks for your answer. It’s weird that I had this problem whereas I was already on 1.5.2 before updating (it was my first update, I got 1.5.2 when I activated n8n for the first time), but the name was still the old one (from before 1.5.1) 🤔

About my “comment” (it wasn’t really a complaint 😀), as I said, I know you do your best, and as I said, you do it pretty well in my humble opinion!

However, it is sometimes complicated to keep everything working after updates (you’ve seen I also encountered problems with the python API after this update), that’s why [I opened this thread](https://forum2.seatable.io/t/how-to-keep-seatable-in-production-when-api-version-changes/4935) to see how it could be possible to think together of a solution to avoid side effects. As you answered me, this is a particular and pretty rare situation as it is a major version update.

Anyway, for this particular problem, it was disturbing, but no big deal to fix.

Bests,  
Benjamin

---

<div class="post-metadata">

**Author:** ![lcx\_at](https://forum.seatable.com/user_avatar/forum.seatable.com/lcx_at/32/2402_2.png) [@lcx\_at](https://forum.seatable.com/u/lcx_at)\
**Post date:** [September 6, 2024, 5:00pm UTC](https://forum.seatable.com/t/n8n-action-node-type-changed/4961/4 "2024-09-06T17:00:12Z")

</div>

ouch … I’ve got about 20 Workflows that I have to fix, thanks @bha for the hint about replacing the name in the exported json.  
Here’s how I did it on a mac,

1. copy the workflow
2. run this in a terminal

```bash
pbpaste |sed -e s/n8n-nodes-seatable.seatable/n8n-nodes-seatable.seaTable/g|pbcopy

```

then remove the workflow and paste what you’ve got in the clipboard.

---

<div class="post-metadata">

**Author:** ![system](https://forum.seatable.com/uploads/default/original/1X/04603423fe81a46c321283663086c475429e8ccb.png) [@system](https://forum.seatable.com/u/system)\
**Post date:** [September 8, 2024, 5:00pm UTC](https://forum.seatable.com/t/n8n-action-node-type-changed/4961/5 "2024-09-08T17:00:46Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
