# 🧮 Feature Suggestion: Query from external database and create types and entities **URL:** \ **Category:** Integrations\ **Created:** [August 21, 2021, 6:16am UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925 "2021-08-21T06:16:12Z")\ **Posts on this page:** 14\ **Page:** 2
**Author:** ![alliancewav](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alliancewav/32/6583_2.png) [@alliancewav](https://community.fibery.io/u/alliancewav)\ **Post date:** [April 24, 2025, 9:21pm UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/21 "2025-04-24T21:21:08Z")
We’d love to see a native Supabase/Postgres integration as an alternative to Airtable! Airtable’s API rate limits make real-time data refresh or sync really tough. Fibery’s Postgres reports feature works great for querying, but it doesn’t let you import or convert that data into native Fibery records. We tried building a link between our Supabase DB and Fibery with n8n, but couldn’t get it to work reliably. A first-party Supabase/Postgres connector or an official n8n node would fit Fibery beautifully! ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [April 25, 2025, 8:55pm UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/22 "2025-04-25T20:55:07Z")
We ended up building a custom app hosted on Vercel which pulls from our Supabase (Postgres) and updates Fibery. Has been a game changer for us. Additionally, Fibery has webhooks integration (which we are still in the process of implementing) for realtime updates. That being said, the setup is more complex than a native integration and I believe Fibery is missing out on a big opportunity here to help Enterprise customers sync and import raw data with ease. Either way, we’ve made it work for us. If interested, I can make some time to open source the integration we made for our custom app. ---
**Author:** ![karthikk\_vijay](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/karthikk_vijay/32/1220_2.png) [@karthikk\_vijay](https://community.fibery.io/u/karthikk_vijay)\ **Post date:** [June 26, 2025, 10:11am UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/23 "2025-06-26T10:11:55Z")
Would really appreciate the open source effort for this one 🙏 ---
**Author:** ![Hendrik](https://avatars.discourse-cdn.com/v4/letter/h/839c29/32.png) [@Hendrik](https://community.fibery.io/u/Hendrik)\ **Post date:** [July 14, 2025, 11:39am UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/24 "2025-07-14T11:39:01Z")
> [@Illusory](#): > > The ability to sync with a Postgres database and directly view and/or edit said database > [@alliancewav](#): > > We’d love to see a native Supabase/Postgres integration Would just like to second this! My understanding is that Fibery uses Postgres. Integration (incl live sync) with other Postgress databases seems a logical step (?) I love the idea that we can replicate live data in a separate open source tool that we can port to any other tool should we need to, instead of relying on CSV exports / backups. I love Fibery but relying on any single private company for data is always risky. Just to add, specifically thinking of Supabase integration. ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [July 14, 2025, 12:12pm UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/25 "2025-07-14T12:12:15Z")
> [@karthikk\_vijay](#): > > Would really appreciate the open source effort for this one 🙏 Will make some time for this! > [@Hendrik](#): > > Would just like to second this! > My understanding is that Fibery uses Postgres. Integration (incl live sync) with other Postgress databases seems a logical step (?) > > I love the idea that we can replicate live data in a separate open source tool that we can port to any other tool should we need to, instead of relying on CSV exports / backups. I love Fibery but relying on any single private company for data is always risky. > > Just to add, specifically thinking of Supabase integration. I agree. Fibery already allows you to sync Postgres within their Reports feature. Seems like the logical next step (Postgres, Supabase, Neon) sync to Fibery Databases/Entities. I’ve been advocating this for years but I don’t believe Fibery team sees the value 🤷‍♂️ Data has always been key and even more so now with AI. Being able to natively sync external databases with Fibery would increase customer lock-in, since they’d easily import massive amounts of business critical data without any effort (like building a custom app). It would enable businesses to build Fibery processes around their core backend data, create new relationships and now with Fibery Smart Agent, analyze. ---
**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:** [July 14, 2025, 12:48pm UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/26 "2025-07-14T12:48:58Z")
I think there are two different cases here: **Syncing data into Fibery** > [@Illusory](#): > > Data has always been key and even more so now with AI. Being able to natively sync external databases with Fibery would increase customer lock-in, since they’d easily import massive amounts of business critical data without any effort (like building a custom app). It would enable businesses to build Fibery processes around their core backend data, create new relationships and now with Fibery Smart Agent, analyze. **Syncing/exporting/backing up data out of Fibery** > [@Hendrik](#): > > I love the idea that we can replicate live data in a separate open source tool that we can port to any other tool should we need to, instead of relying on CSV exports / backups. I love Fibery but relying on any single private company for data is always risky. The topic title and original post is about the former, whereas @Hendrik seems interested in at least the latter, which should probably be a separate topic. ---
**Author:** ![Hendrik](https://avatars.discourse-cdn.com/v4/letter/h/839c29/32.png) [@Hendrik](https://community.fibery.io/u/Hendrik)\ **Post date:** [July 14, 2025, 1:40pm UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/27 "2025-07-14T13:40:05Z")
> [@Chr1sG](#): > > The topic title and original post is about the former, whereas @Hendrik seems interested in at least the latter, which should probably be a separate topic. Agreed. Since we are starting from scratch, we need to make architectural decisions from the start that would make sense for redundancy - sync out / backup. However, while we have data in Postgres, we would love to be able to, for instance, capture data in the field on a simple mobile app to the ‘root’ Postgres database, which should sync back into Fibery. So I see significant benefeit to bi-directional syncing. And it’s simple to create such an app that can sync with Supabase for instance. To us, this would be better than to have a Fibery app which would have to be focused on Fibery’s core mission (and probably not let us distribute a simple app to clients or agents without the requirement for 20 additional Fibery subscriptions for a simple task). A decoupled database is just so much better to my mind. ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [July 14, 2025, 2:12pm UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/28 "2025-07-14T14:12:05Z")
> [@Hendrik](#): > > So I see significant benefeit to bi-directional syncing. Here ya go 🙂 The bottom line: Fibery would benefit from **any level** of native syncing with external database systems… ---
**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:** [July 14, 2025, 2:27pm UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/29 "2025-07-14T14:27:24Z")
> [@Illusory](#): > > The bottom line: Fibery would benefit from **any level** of native syncing with external database systems… I don’t doubt that, but if we’re trying to gauge demand (and to determine a solution that satisfies the most people) it makes sense to split the use cases in two. There might be more people who are very interested in a ‘live’ backup (to Postgres or even to some other non-proprietary format) than people who are interested in syncing their existing data from Postgres into Fibery. For what it’s worth, a bidirectional sync is unlikely to happen for many months (probably even years, if ever). ---
**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:** [July 14, 2025, 5:20pm UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/30 "2025-07-14T17:20:30Z")
@Hendrik you mentioned that it’s simple to create an app that can sync with supabase, and @Illusory has said that they made a supabase custom integration. Sounds like you could team up to get something working that satisfies your needs for Mobile ↔ Postgres → Fibery syncing? As for this: > [@Illusory](#): > > Fibery is missing out on a big opportunity here to help Enterprise customers sync and import raw data with ease we are always open to developing features for our Enterprise customers, so if that’s your situation, reach out to us directly. ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [July 14, 2025, 10:16pm UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/31 "2025-07-14T22:16:24Z")
I will make it open source as soon as possible. > [@Illusory](#): > > the setup is more complex I don’t think it’s simple (in fact, I mentioned that it was more complex). Although we’re generally happy that we were able to create our own custom solution, it was not without aches and pains (e.g. we still have to manage separate infra and codebase for the purpose of syncing and still haven’t gotten webhooks to work properly). My aim is here in the forum is almost always to promote or suggest features that I think could be of benefit to many Fibery users, not just for our specific use cases. I don’t expect this to be implemented but I still think it could be very valuable. ---
**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 18, 2025, 1:03pm UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/32 "2025-12-18T13:03:59Z")
> [@helloitse](#): > > I’ve been thinking through when I might ever find the time to integrate Stripe with Fibery. Implemented in latest release [December 18, 2025 / 🎁 Fibery iOS and Android apps, Custom Database access, Stripe integration, Architect mode](https://community.fibery.io/t/december-18-2025-fibery-ios-and-android-apps-custom-database-access-stripe-integration-architect-mode/10183) ---
**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 30, 2026, 8:39am UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/33 "2026-10-30T08:39:00Z")
This problem solved via AI Connectors [AI Connectors: creating custom integrations](https://the.fibery.io/@public/User_Guide/Guide/AI-Connectors-creating-custom-integrations-488) ---
**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 30, 2026, 8:48am UTC](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925/34 "2026-10-30T08:48:45Z")
Closed on October 30, 2026, 8:48am UTC [Previous page](https://community.fibery.io/t/feature-suggestion-query-from-external-database-and-create-types-and-entities/1925.md?page=1)