# Let multiple Fibery Integrations Write to The Same Database

**URL:** <https://community.fibery.io/t/let-multiple-fibery-integrations-write-to-the-same-database/10847>\
**Category:** Integrations\
**Created:** [May 13, 2026, 8:23pm UTC](https://community.fibery.io/t/let-multiple-fibery-integrations-write-to-the-same-database/10847 "2026-05-13T20:23:27Z")\
**Posts on this page:** 1\
**Page:** 1

<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:** [May 13, 2026, 8:23pm UTC](https://community.fibery.io/t/let-multiple-fibery-integrations-write-to-the-same-database/10847/1 "2026-05-13T20:23:27Z")

</div>

Fibery allows integrations to create dedicated databases that actually are the same type of data (_aside: I do think types was a better name_ IYKYK).  
Today, the restriction of needing one email table per integration is an outdated approach. It’d be great to see Fibery add a sync layer to integrations so we can have multiple integrations share a database. For example:

- The Google Calendar and Gmail integrations would be able to share the same emails database.
- Or Paypal and Stripe can write to the same Payments database.  
This would simplify the Fibery navigation and implementation experience for users.