Guide
What is an Automation Rule and a Button
There are two types of automations in Fibery: Automation Rules and Buttons:
Automation Rules are Automations where the trigger is an event occurring in Fibery. For example, you can define an Automation Rule that sets the completion date to today when a task is closed.
Buttons are Automations that is triggered manually. For example, you can create a "Finish Sprint" Button that when clicked moves all unfinished tasks to the next sprint.
How to add an Automation
To add an Automation:
Go to a Space Configuration
Choose a Database and expand it.
Find Automation Rules or Buttons section and click + near it.
Things you can do to Automation Rules and Buttons
Duplicate
Duplicate action is available for automation rules and buttons, so you can easily iterate on your existing automation rule configuration or create a similar button. Click … near an automation rule and select Duplicate action.
Reorder
You can drag and drop automation rules and buttons to organize them better.
It will also affect automation rules execution order.
Add a description
You can add a description to automation Rules and Buttons. It will help to understand what the automation rule is about, and for buttons it will show a tooltip when a user hovers over the button.
Duplicate Automations across Databases
Sometimes the same automation logic is needed in multiple databases — for example, applying identical automation rules to both Bugs and Features. Instead of recreating automations from scratch, you can duplicate an existing automation and apply it to another database.
The Duplicate to… action allows you to copy an automation rule from one database to another.
The current database is selected by default
You can choose a different target database from the selector
Once selected, the automation is duplicated and applied to that database
Automation duplication assumes that the target database is structurally compatible with the source one.
This means:
Fields used in the automation must exist in the target database
Field names and types should match
It’s the admin’s responsibility to align schemas before duplicating
If a field used in the automation does not exist in the target database, it is treated as if the field was deleted.
What happens if something is missing
If the duplicated automation references fields or elements that don’t exist in the target database:
In some cases, actions that can’t be resolved may be removed or marked as invalid after duplication.
Limitations
Users database is excluded — automations cannot be duplicated to or from it
There is no automatic field mapping or conversion
This feature is intended for databases with intentionally aligned schemas
When to use Automations
For inspiration, please check most popular Automations Use Cases and Examples.
Also, Fibery has built-in AI Assistant, so check AI in Automations to learn how to do clever things with AI.
Who can configure Automations
Anyone with Architect access to a Space can set up no-code Automation Rules and Buttons for Databases in the Space. Scripts in Automations are reserved for workspace Admins.
Check out Automation permissions for a detailed breakdown.