Guide
Using Slack Integration, you can import Slack messages from different channels into Fibery for further processing.
This is done through a synchronization process that is event and time-based. This means messages and reactions will show up on Fibery immediately, but some information will be synced by pulling it from Slack Workspace at regular intervals. This approach helps to ensure the integrity of the information.
You can also check the Slack Actions and Notifications for more tips.
Please, note that:
Set up the integration
Click your workspace name → Settings → Integrations.
Click Sync and select Slack.
Authenticate with OAuth or paste a personal API token.
Approve the permission request.
Configure the integration:
Channels - select which Slack channels to sync. Archived and private channels aren't supported.
Oldest message - messages before this date won't sync.
User messages only - enable to exclude messages from the Fibery bot.
Configure which databases and fields to sync.
Click Sync now to start the first sync.
Archived channels will also be listed in the dropdown menu but NOT included in the synchronization process.
Please be aware that private channels are NOT supported for security reasons.
Add the Fibery bot to your channels
Before the first sync, the Fibery Slack bot (named @Fibery Automation by default) must be a member of every channel you've selected. Mention the bot's name in the channel, then click Add to Channel.
If the bot isn't added, the sync will fail.
Next steps
See Slack Actions and Notifications for automating based on synced messages.
Slack integration reference
Sync behavior
Messages and reactions sync in real time. Users, user groups, and channels sync at regular intervals.
⚠️ Slack announced API rate limit changes for March 2026 that affect sync. Update this note with current status before publishing.
Databases
Database | What it contains |
|---|
Message | One entry per message sent in a configured channel |
Reaction | One entry per emoji reaction (each use counts separately, even for the same emoji on the same message) |
Channel | One entry per configured channel |
User | Every user in the Slack workspace |
User Group | Every user group in the Slack workspace |
Configuration options
Option | Description |
|---|
Channels | Slack channels to sync messages from. Archived and private channels aren't supported. |
Oldest message | Messages sent before this date aren't included. |
User messages only | Filters out messages from the Fibery Slack bot during sync. |
Supported objects
Slack object | Status | Notes |
|---|
Message | ✅ Supported | |
User | ✅ Supported | |
User Group | ✅ Supported | |
Channel | ⚠️ Partial | Archived and private channels aren't supported |
Canvas | ❌ Not supported | |
Limitations
User avatars don't sync.
User and user group mentions in messages aren't linked to their Fibery database entries.
Link previews (pasted Slack message URLs from another channel) aren't captured.
Fibery's Slack app isn't listed in the Slack App Directory. Organizations that block non-approved apps can't use this integration.
Troubleshooting
You may encounter the following issues when setting up or syncing with the Slack integration. Follow the instructions below to resolve them.
Ensuring that data loss does not occur during the synchronization process is critical, and handling synchronization errors is vital. Our synchronization framework is designed to halt the process if the issue cannot be resolved automatically. To avoid further complications, we do not automatically remove any channel or change the configuration when a problem arises. If you need to change the configuration, for example, if the Slack channel has been deleted, you can move or export the database. This is important because any data from non-configured channels will be deleted when the sync restarts.
Fibery Slack Bot is not a member of one of the selected Slack channel
Fibery Slack Bot is not a selected channel(s [channel(s)] member. Please invite the bot to the channel to sync messages and reactions.
Removing Fibery Slack Bot from the channel will permanently delete all previous channel information, messages, and reactions from the Fibery databases.
If you are having trouble with the Fibery Slack bot, it might be because the bot is not added to the configured Slack channels. To fix this, please check Step 8 in this guide and ensure that the Fibery Slack bot is added as a member of the relevant channels.
If the Fibery Slack Bot has been removed from the channel and you do not want to add it back, you can remove the channel from the setting. But do note that removing the channel will also delete all channel-related information, including conversations and reactions. Therefore, exporting or moving any necessary information elsewhere is important before removing the channel if you want to keep the data.
No Channel selected
No channel has been selected. Please specify the channel in the configuration when selecting a message, reaction, or channel.
While setting the channel is optional in the configuration, it becomes mandatory when you want to sync messages, reactions, or channels. So, if any of these databases are enabled, please also specify the channel. Otherwise, the sync will not work.
Configured Slack channel is archived
The Fibery Slack Bot is not a selected channel(s) [channel(s)] member because it has been archived. To sync messages and reactions, please unarchive the Slack channel and reinvite the Slack bot to the channel.
Removing the channel from the configuration will permanently delete all previous channel information, messages, and reactions from the Fibery databases.
When a Slack channel is archived, we can no longer sync information. This means the synchronization will stop, and you will need to unarchive the channel from the configuration if you want to keep the channel information synced.
However, if you remove the channel from the sync, all the channel messages and reactions will also be deleted. Therefore, if you want to keep the data, it is important to export or move any necessary information elsewhere before removing the channel.
Insufficient permission for Fibery Slack Bot
Fibery Slack Bot requires additional permissions for full functionality. Please recreate the account with the necessary permissions and attach it to the integration.
This issue occurs when necessary permissions were not granted during Fibery Slack Bot installation in the Slack Workspace or were changed afterward. To start or restart the sync, this issue must be resolved.
Configured Slack channel is deleted
The previously configured channel is no longer accessible. This may be because it was deleted or set to private. Please fix the configuration by removing unavailable channels or making them available again.
Removing the channel from the configuration will permanently delete all previous channel information, messages, and reactions from the Fibery databases.
When a Slack channel is deleted, we can no longer sync its information. This means the synchronization will stop, and you must remove the channel from the configuration if you want to keep the channel information synced.
However, if you remove the channel from the sync, all the channel messages and reactions will also be deleted. Therefore, if you want to keep the data, it is important to export or move any necessary information elsewhere before removing the channel.
Slack says the Fibery app is not approved for use - can we still connect it?
Unfortunately, Fibery’s Slack app will not be approved by Slack, as our intended use case doesn’t comply with their app approval policies.
This means the app cannot be listed in the Slack App Directory, and some organizations may block its use entirely based on their internal security or compliance rules. If Slack is rejecting the connection, your organization may not be able to use the integration at this time.
How do I switch system notifications to a new Slack workspace?
Go to the Notifications page (not the Integrations page) and connect the new Slack account from there. Reconnecting a Slack account under Integrations only affects the data sync - it doesn't update where system notifications are sent.
Build User inventory
Synchronizing user information from different third-party systems to keep track of the number of users in each system, their identities, and costs is feasible.
Numerous companies rely on Slack’s user database as one of the best-maintained sources of user information. Slack user information can be imported or synced into a Fibery database by integrating the two platforms. This will allow you to develop a backbone of user information in Fibery.
You only need to synchronize the User and User groups database to achieve this