Guide
Collect feedback from Slack Messages
By capturing feedback through Slack, product teams can make data-driven decisions and continuously improve their products. However, by manually transferring the feedback to other tools, they may be missing out on opportunities to innovate and streamline their processes.
Fibery's Slack integration enables easy collection of Slack messages, streamlines feedback processes, and creates references with product features and insights. This is similar to Fibery's Intercom integration and Discourse integration .
Fibery is configured to collect messages in real time from the designated Slack channels. The messages are then added to a structured database in Fibery that includes crucial information such as sender, time, reactions, the message itself, and many more. For example, you may have #feedback channel in your team Slack so you can fetch all messages from this channel to Fibery.
Storing all this information in the Fibery databases allows for easy filtering and sorting of messages, and different views can be created for improved organization. Furthermore, automation can be built on top of it.
The messages are saved in rich text format, which can be linked to other databases such as features or insights. By connecting this information, better product decisions can be made.
Check the Slack Actions and Notifications for more tips.
Slack Integration Overview
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.
Setup
Create a Space.
Navigate to Space settings and click Integrate button.
Select Slack.
Authentication of your Slack account can be done through OAuth (recommended), but you may use a personal API auth token if you prefer.
Allow the permission request.
Customize the Integration settings.
Databases
Message: Each message sent in a configured Slack channel is recorded as a single entry in the Message database.
Reaction: Each use of an emoji represents a separate entry, even if it's used multiple times in the same message.
Channel: Each configured Slack channel is counted as one entry.
User: Every user in the Slack workplace.
User Group: Every workgroup in the Slack workplace.
Channels
Select the Slack channels that you want to collect messages from.
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.
Oldest Message
Any messages sent before that date will not be included.
User Messages Only (Filter out Fibery Bot messages)
Enabling this option filters out the Slack messages and replies from the Fibery Slack Bot during synchronization.
Set up Fields and Databases.
The provided Slack fields by the integration can be mapped and configured to the Fibery integration database.
Click on the Sync now button to start the sync process.
Add Fibery Slack Bot to the channels.
Before starting the synchronization process, invite the Fibery Slack Bot to all the channels you have set up. Otherwise, you will receive an error message indicating that the synchronization setup could not be completed.
All you need to do is mention the name (@Fibery Automation by default) of the Bot in the channel, and click on the Add to Channel button to approve it.
Start the sync
Once you finish configuring, save and click Sync now to start synchronization.
Supported objects, fields, and the default mapping
Fibery supports syncing the following type of information/object from Slack Workspaces.
Slack | Status | Fibery Integration/Import |
Channel | ⚠️ | partly — archived and private channels are not supported |
Message | ✅ | supported |
User | ✅ | supported |
User Group | ✅ | supported |
Canvas | ❌ | not supported |
Database structure
Channel: Every configured Slack channel is one entry.
Slack field | Type | Fibery field | Description |
Name | Name | Name | Name of the Channel, mandatory field |
Archived | Checkbox | Archived | Represent the Slack channel archive status |
Message: Every single message in the configured Slack channel(s) is one entry.
Slack field | Type | Fibery field | Description |
Name | Name | Name | Generated from Message (first x character), mandatory field |
Channel Id | Relation | Channel | The Channel where the Message is. Message has one Channel |
Date | Date and Time | Date | Message creation date in Slack (not in Fibery) |
Files | Files | Files | Slack message attachment(s) |
Message Id | Text | Message Id | Unique message identifier |
Order | Decimal number | Order | Message order |
Root Message Id | Text | Root Message Id | Unique identifier of the root message |
Thread Id | Relation | Thread / Replies | The parent message of the message. If there is no parent, this is empty. Message has one Message |
URL | URL | URL | The permanent link to the Slack message |
User | Relation | User | The sender of the message. Message has one User |
Name | Name | Name | Generated from Message (first x character), mandatory field |
Reaction: Every emoji is one entry, even for the same message.
Slack field | Type | Fibery field | Description |
Name | Name | Name | Emoji names with semicolons, mandatory field |
Message | Relation | Message | Emoji on the message. Reaction has one Message. |
User | Relation | User | Creator of the emoji. Reaction has one User. |
User: Every user of the Slack workplace.
Slack field | Type | Fibery field | Description |
Name | Name | Name | Slack User name mandatory field |
Bot | Checkbox | Bot | Indicates whether the user is a bot user. |
Deleted | Checkbox | Deleted | When the value is true the user is deactivated. |
Display Name | Text | Display Name | Display Name of the Slack user |
Email | Email | Email | Email address of the Slack User |
First Name | Text | First Name | The user's first name. |
Last Name | Text | Last Name | The user's last name. |
Phone | Text | Phone | The user's phone number, in any format. |
Title | Text | Title | The user's title. |
Usergroup: Group of users with one handle address
Slack field | Type | Fibery field | Description |
Name | Name | Name | Slack Usergroup name mandatory field |
Description | Rich Text Markdown | Description | Explains the purpose of the group |
Handle | Text | Handle | Indicates the value used to notify group members via a mention without a leading @ sign. |
Users | Relation | User | Member of the users |
Understanding and Resolving Errors
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.
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 Usergroups database to achieve this.
Known issues
Slack user avatar sync is not supported.
User or user group mentions in Slack messages are not processed to connect to the database and entities.
The preview of Slack messages from another channel (when you paste a link) is not supported. This is because link previews in Slack are mainly intended for visual enhancement and not for storing and retrieving data.
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.