# IaaS tools that already have Fibery support?

**URL:** <https://community.fibery.io/t/iaas-tools-that-already-have-fibery-support/8174>\
**Category:** API & Programming\
**Created:** [January 24, 2025, 2:54pm UTC](https://community.fibery.io/t/iaas-tools-that-already-have-fibery-support/8174 "2025-01-24T14:54:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mturquette](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mturquette/32/7699_2.png) [@mturquette](https://community.fibery.io/u/mturquette)\
**Post date:** [January 24, 2025, 2:54pm UTC](https://community.fibery.io/t/iaas-tools-that-already-have-fibery-support/8174/1 "2025-01-24T14:54:01Z")

</div>

Hi all,

My team has used [Make.com](http://Make.com) to create some integrations between 3rd party tools and Fibery, but there are some limitations with this approach.

I have been looking at IaaS solutions like [n8n.io](http://n8n.io), and I haven’t found much “native” support for Fibery like there is in Make. I’m aware that every Fibery instance will have a custom DB so it will always be necessary to map fields manually within the IaaS tool, but I was really hoping to at least get some pre-built support for authentication and establishing the initial connection. Otherwise we’ll have to write a module from scratch, which does not sound fun or efficient.

Any pointers to other integration tools that are a strong fit for Fibery?

Thanks,  
Mike

---

<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:** [January 24, 2025, 3:00pm UTC](https://community.fibery.io/t/iaas-tools-that-already-have-fibery-support/8174/2 "2025-01-24T15:00:47Z")

</div>

> [@mturquette](#):
>
> My team has used [Make.com](http://Make.com) to create some integrations between 3rd party tools and Fibery, but there are some limitations with this approach.
> 
> I have been looking at IaaS solutions like [n8n.io](http://n8n.io)

My understanding is that n8n has similar functionality to [make.com](http://make.com), so I am wondering what the limitations you have experienced are?

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [January 24, 2025, 3:31pm UTC](https://community.fibery.io/t/iaas-tools-that-already-have-fibery-support/8174/3 "2025-01-24T15:31:46Z")

</div>

The search query module in Make only allows for exact matching of values. I regularly use the API module instead but this creates errors when the schema changes in Fibery that take more manual work to fix.

Some API actions (like files or batch endpoints) don’t have modules

---

<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:** [January 24, 2025, 3:41pm UTC](https://community.fibery.io/t/iaas-tools-that-already-have-fibery-support/8174/4 "2025-01-24T15:41:05Z")

</div>

Are these issues present in make, but not present in n8n?

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [January 29, 2025, 5:34pm UTC](https://community.fibery.io/t/iaas-tools-that-already-have-fibery-support/8174/5 "2025-01-29T17:34:13Z")

</div>

Unfortunately, I don’t have any experience with n8n but figured I can speak to limitations in make