Guide
Our Slack Bot lets you create and manage entities without leaving Slack. It supports:
Creating entities from Slack messages
Creating entities with /fibery commands
Viewing your assigned entities
Triggering Fibery actions from Slack Workflows
Set up the Slack Bot
Note: Slack connection requires admin access in both Fibery and Slack.
In Fibery, go to Templates → Integrations.
Find Slack Bot and click Connect.
Authenticate with your Slack account.
Go to Settings → Notifications and turn on Slack Notifications.
Note: Fibery Bot only sends DMs - it can't post to specific channels directly.
How to create an entity from a Slack message
Hover over a message in Slack and click the More actions (⋯) menu.
Select Create Entity.
Choose the target database (e.g. Task, Bug, Feature).
If the message contains an image, it's automatically attached to the entity - useful for reporting bugs from screenshots 🐛.
To enable options to attach images, you need to add the Fibery app to the channel first:
Click the channel name.
Go to Integrations.
Find Fibery and click Add.
Long messages can be saved into rich text fields.
Note: you can save large messages in rich text fields.
How to set up a Slack Workflow with Fibery steps
If the Fibery Slack Bot isn't installed, go to Fibery → Templates, find Slack Bot and connect it. If it's already installed, re-install it using this link.
Fibery supports several workflow steps:
Find entity
Create entity
Update entity
Example: create a Fibery entity when a message is posted in a channel
In Slack, click + and select Workflow.
Set the trigger to When message is posted.
Add a step: Fibery → Create an Entity.
Select your Fibery workspace and database.
Map the field values (e.g. set Name from the message text).
Save and Publish the workflow.
See Slack's workflow documentation for more.
Note that some field types are not supported:
How to connect multiple Fibery workspaces
If your team uses multiple Fibery workspaces with one Slack workspace, set a default workspace with:
/fibery set-default-workspace [workspace_name].fibery.io
To check the current default:
/fibery me
Output example:
Workspace: the.fibery.io (default)
User: Michael Dubakov
Command reference
All commands use /fibery (or your workspace-specific prefix, e.g. /fiberyedge).
Create entities
/fibery create <database> "<entity name>"
/fibery create bug "login page crashes on submit"
/fibery create task "record the video about Slack Bot" @john
/fibery create feature "Notifications"
To assign a user, use @ — works when the email in Slack matches the email in Fibery. If the database has multiple People fields, specify the field name:
/fibery create bug "Text" @michael dubakov as QA
/fibery create bug "Text" @michael dubakov as Product Owner
View your assigned entities
/fibery my <database>
/fibery my bugs
/fibery my "user stories"
/fibery my "Marketing/Task"
Vacations and sick days
Requires the Vacations Space. The bot parses natural language dates and shows a confirmation before logging.
/fibery day off today
/fibery day off tomorrow
/fibery half day off Jun 13
/fibery vacation Jun 10–20
/fibery sick today
Note: If you rename databases in the Vacations template, these commands may break. Stick to the original names until customization is fully supported.
Vacation channel (admins only)
/fibery set vacation channel # Set current channel to receive team vacation updates
/fibery reset vacation channel # Remove the vacation channel
/fibery get vacation channel # Show the current vacation channel
FAQ
I changed my email and stopped receiving notifications.
Make sure your email in Fibery and in Slack match exactly. Once they do, notifications resume automatically.
A non-admin user can't see the connected Slack app when editing an automation rule.
For security reasons, the connected Slack account is only visible to whoever added it. The user editing the rule needs to connect their own Slack account (or re-use the same account if they have permissions to do so).