# \[DONE\] N8n integration

**URL:** <https://community.fibery.io/t/done-n8n-integration/1439>\
**Category:** Integrations\
**Created:** [March 11, 2021, 5:22am UTC](https://community.fibery.io/t/done-n8n-integration/1439 "2021-03-11T05:22:46Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajayjohn](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ajayjohn/32/1587_2.png) [@ajayjohn](https://community.fibery.io/u/ajayjohn)\
**Post date:** [March 11, 2021, 5:22am UTC](https://community.fibery.io/t/done-n8n-integration/1439/1 "2021-03-11T05:22:46Z")

</div>

Could you please build a native integration to n8n ([https://n8n.io/](https://n8n.io/))?  
Not only is this a much more powerful tool than Zapier and Integromat, but, it also supports on-premise installations and functions similar to advanced tools like Node-Red.

---

<div class="post-metadata">

**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\
**Post date:** [March 13, 2021, 8:17pm UTC](https://community.fibery.io/t/done-n8n-integration/1439/2 "2021-03-13T20:17:43Z")

</div>

Hi!  
Telling the truth, that is the first request like this 🙂  
So, noted and we will see whether that tool will be popular 💖

Btw, many thanks for the idea - checked it, pretty nice one!

---

<div class="post-metadata">

**Author:** ![carson](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/carson/32/7503_2.png) [@carson](https://community.fibery.io/u/carson)\
**Post date:** [November 21, 2023, 8:57pm UTC](https://community.fibery.io/t/done-n8n-integration/1439/3 "2023-11-21T20:57:50Z")

</div>

I’m in the initial stages of going ahead and building a community node for n8n. One unique thing about Fibery’s query commands are that they are (seemingly) infinitely nestable.

Building this functionality into a nice GUI for n8n is going to be challenging, and I’m still deciding exactly what features to build and when.

I am pretty sure that right now, however, it would be useful to have a parser/linter that can validate whether or not the JSON command syntax is correct. I’m sure there’s some form of that happening on Fibery’s back end. Is that something you’d ever be willing to publish or share with me for n8n implementation?

---

<div class="post-metadata">

**Author:** ![dukevannori](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@dukevannori](https://community.fibery.io/u/dukevannori)\
**Post date:** [November 25, 2023, 10:51pm UTC](https://community.fibery.io/t/done-n8n-integration/1439/4 "2023-11-25T22:51:29Z")

</div>

i have built an obsidian importer and a Google contacts updater from a CRM

it’s great and with the API calls it’s already very possible to do a lot

the json can be tricky though

---

<div class="post-metadata">

**Author:** ![GAA](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/gaa/32/9437_2.png) [@GAA](https://community.fibery.io/u/GAA)\
**Post date:** [May 30, 2024, 8:06am UTC](https://community.fibery.io/t/done-n8n-integration/1439/5 "2024-05-30T08:06:36Z")

</div>

Interested aswell by a n8n integration, keeping an eye on the thread!

---

<div class="post-metadata">

**Author:** ![Robert\_Peter\_Valu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/robert_peter_valu/32/11029_2.png) [@Robert\_Peter\_Valu](https://community.fibery.io/u/Robert_Peter_Valu)\
**Post date:** [May 16, 2025, 2:08pm UTC](https://community.fibery.io/t/done-n8n-integration/1439/6 "2025-05-16T14:08:25Z")

</div>

+1 to having an n8n integration

---

<div class="post-metadata">

**Author:** ![inn0minatus](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/inn0minatus/32/11751_2.png) [@inn0minatus](https://community.fibery.io/u/inn0minatus)\
**Post date:** [May 18, 2025, 2:13pm UTC](https://community.fibery.io/t/done-n8n-integration/1439/7 "2025-05-18T14:13:45Z")

</div>

n8n is experiencing a massive surge in popularity right now. Take my vote!

---

<div class="post-metadata">

**Author:** ![timothy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/timothy/32/11812_2.png) [@timothy](https://community.fibery.io/u/timothy)\
**Post date:** [May 28, 2025, 3:06am UTC](https://community.fibery.io/t/done-n8n-integration/1439/8 "2025-05-28T03:06:25Z")

</div>

Adding my vote here

---

<div class="post-metadata">

**Author:** ![Oleksander\_Korin](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oleksander_korin/32/11815_2.png) [@Oleksander\_Korin](https://community.fibery.io/u/Oleksander_Korin)\
**Post date:** [May 28, 2025, 3:25pm UTC](https://community.fibery.io/t/done-n8n-integration/1439/9 "2025-05-28T15:25:05Z")

</div>

another vote for n8n integration - my team is literally considering a different tool for CRM because of lack of n8n integration out of the box

---

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [May 28, 2025, 3:47pm UTC](https://community.fibery.io/t/done-n8n-integration/1439/10 "2025-05-28T15:47:22Z")

</div>

Yes, I’m very in favor of n8n integration.

…but n8n brings what could partly be covered by, or made easier by, Fibery. **A lot of people use n8n but mostly tech-savvy workflow designers.**  
I think that the trend is now that **‘normal’ users start to understand and use workflow** s, especially because AI makes that easy, without complex technical setup.

So the whole workflow scene is changing from tech-savvy to end-user-friendly.

**So what is the position of Fibery in this?**  
To me it appears that Fibery is very close to being able to offer n8n-like functionality, because of its relationship and automation architecture. I have indicated this opportunity before, see for example:

- [Improving AI Workflow Tools in Fibery - Fibery AI - Fibery.io Community](https://community.fibery.io/t/improving-ai-workflow-tools-in-fibery/7964)
- [Whiteboard-like Automations Setup/Builder - Ideas & Features - Fibery.io Community](https://community.fibery.io/t/whiteboard-like-automations-setup-builder/6563/4)

As well as what I wrote in June 2024:

> [@Allow drag-drop sorting Rules (similar to drag-drop sorting of Access Templates) \[DONE\]](https://community.fibery.io/t/allow-drag-drop-sorting-rules-similar-to-drag-drop-sorting-of-access-templates-done/6303/1):
>
> Note: With the introduction of Highlights, the next logical step is to make Fibery support better workflows to create and make use of that data.
> 
> I think there are three core features of Fibery that drive cycles of intelligent input and output:
> 
> 1. **Data** : Highlights
> 2. **Processes** : Automations (workflows)
> 3. **Insights** : AI Workspace Data Expert
> 
> The Automations feature is in my opinion underdeveloped at this stage.

So with ‘Automation feature underdeloped’ I mean that:

- Old paradigm: Automations are created by admins (mostly)
- New paradigm: end users want and have easy chaining of actions.

So this goes beyond n8n (although n8n is catching up to make it easier too for end users)

I mentioned recently:

> [@What if AI Chat was a field? Or an automation where builder can make their own AI Chat embedded where needed?](https://community.fibery.io/t/what-if-ai-chat-was-a-field-or-an-automation-where-builder-can-make-their-own-ai-chat-embedded-where-needed/8844/7):
>
> So the Smart Agent that Fibery now is building could do a lot, but I think that the management and control of the chained Smart Agent calls is more interesting for Fibery users.

**So there is still a gap between:**

- 
  1. either “Big Smart Agent” does it all for you, or “Space templates” (both are opnionated and give less control)

**..and:**

- 
  1. Automations (currently only for tech savvy people or admins)

That gap is to be filled by Fibery with what I hope is a **graphical n8n-like interface to easily create workflows**. It would perfectly fit Fibery to offer that, and it does not have to be as complex as n8n.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [May 29, 2025, 9:01am UTC](https://community.fibery.io/t/done-n8n-integration/1439/11 "2025-05-29T09:01:40Z")

</div>

We will see how hard it is to implement from our side

---

<div class="post-metadata">

**Author:** ![vkarbovnichy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/vkarbovnichy/32/11849_2.png) [@vkarbovnichy](https://community.fibery.io/u/vkarbovnichy)\
**Post date:** [August 24, 2025, 7:35pm UTC](https://community.fibery.io/t/done-n8n-integration/1439/12 "2025-08-24T19:35:04Z")

</div>

One of our co-founders is quite reluctant to use any task tracking systems (we tried several before stopping on Fibery), and asked “what if I had a bot who tells me everything I need”. It’s a major pain point in our everyday work.

We do automations in n8n for clients, and the obvious idea was to create some workflow there for internal use which handles a Telegram bot. I’ve just thought of using Fibery MCP server (the recently released one) there and was surprised I can’t do that because MCP Server supports only Claude and VSCode “for security reasons”. Well, we have API keys…

Talking specifically about integration with n8n: MCP Server support will be a big step forward while we wait for the full scale integration. Btw we use self-hosted n8n, if that might matter.

PS: I realize I need to try Fibery AI for this use case, let me check that later.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [October 2, 2025, 2:28pm UTC](https://community.fibery.io/t/done-n8n-integration/1439/13 "2025-10-02T14:28:05Z")

</div>

In progress, should be released in October

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 9, 2025, 1:47pm UTC](https://community.fibery.io/t/done-n8n-integration/1439/14 "2025-10-09T13:47:51Z")

</div>

[Beta release today](https://community.fibery.io/t/october-9-2025-manage-everything-shared-publicly-n8n-integration-beta/9770)

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [December 8, 2025, 10:20am UTC](https://community.fibery.io/t/done-n8n-integration/1439/15 "2025-12-08T10:20:21Z")

</div>

Released officially [Fibery integrations | Workflow automation with n8n](https://n8n.io/integrations/fibery/)

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [December 8, 2025, 10:20am UTC](https://community.fibery.io/t/done-n8n-integration/1439/16 "2025-12-08T10:20:36Z")

</div>


