Guide
Integrations in Fibery are quite unusual. It replicates a part of an external app domain and feed data into Fibery and create several Databases.
Dedicated service (integration application) should be implemented to configure and fetch data from an external application.
How it works
All communication between integration application and Fibery services is done via standard hypertext protocols, whether it can be HTTP or HTTPS. All integration applications are expected to adhere to a particular API format as outlined in this documentation. The underlying technologies used to develop these integration applications are up to the individual developer.
Users may register their applications with Fibery by providing a HTTP or HTTPS URI for their service. The service must be accessible from the internet in order for the applications gallery to successfully communicate with the service.
It is highly recommended that service providers consider utilizing HTTPS for all endpoints and limit access to these services only to IP addresses known to be from Fibery.
In essence, Fibery's applications gallery service acts as a proxy between other Fibery services and the third party provider with some added logic for account and filter storage and validation.
Availability for users
Installed application will be available for all users in your Fibery workspace that have either Admin role in workspace, or Architect access in the Space where the application was configured. Users from another workspace won't be able to see or use your integration application.
Once you sync data with this application, you can apply standard Fibery permissions on it.
In the interface, Type = Database, App = Space. To find out why, check Terminology.
Dig deeper
Create Custom Integrations
Custom App: Fields
Custom App: REST Endpoints
Custom App: OAuth
Custom App: Date range grammar
Custom App: Test and debug
Integration Schema types
Integration Filters
Custom App: External actions API (beta)
Custom App: Webhooks (beta)
Tutorials
Simple custom App tutorial
Custom holidays App tutorial
Custom Notion sync App tutorial
FAQ
If my access is revoked, will the Fibery integration stop working?
Yes. The integration relies on the OAuth token of the user who originally set it up.
If your account is deactivated or your permissions are lowered so you no longer have API access, the token becomes invalid.
Fibery will no longer be able to "authenticate," and the sync will stop.
Will my previously synced data be deleted?
It depends on who restores the connection. Fibery follows a "safety-first" approach where records stay in the system, but "Deleted in App" status is sensitive to the permissions of the new Integration Owner.
If the original user restores the connection, a full sync runs and all data remains intact.
If a different user (e.g., Jane instead of John) reconnects the integration, Fibery respects the new user's permissions in the source app:
If the new owner has less access than the original owner, any records they cannot "see" in the source app will either disappear from the view or be marked as Deleted in App = Yes.
Records accessible to the new owner will stay synced and continue to receive updates.
How can I prevent the integration from breaking?
To ensure a permanent, stable sync, we recommend one of the following:
Set up the integration using a generic "system" or "service" user (e.g., fibery-sync@yourcompany.com) with high-level administrative access. This account is unaffected by individual staff turnover.
Before an admin leaves, a permanent Admin with identical or greater permissions should go to the Integration settings in Fibery and click "Reconnect" or "Update Credentials."
When changing the integration owner, always ensure the new owner has a "Super Admin" or equivalent role in the source app to prevent records from being marked as "Deleted" due to permission gaps.