@mdubakov Looks Like I am late to the party.
In my opinion, Fibery Automations have significant room for improvement. I’ll break my thoughts into two areas: Automation Workflows and Automation Rules.
Automation Workflows (Flows)
A Flow is a sequence of rules working together to accomplish one larger process. Fibery doesn’t currently support this concept in a convenient way. To simulate a flow, you must create a separate rule for each event — which becomes cumbersome for complex processes like email nurture sequences.
Flows can occur instantly (e.g., on a state change) or over time (e.g., in a drip campaign). While Fibery can technically handle both with multiple rules, managing these rules quickly becomes difficult.
Ideal Feature:
A visual “Flow Builder” where clicking a rule opens its corresponding Fibery automation would make this far more intuitive and maintainable. This builder might not be database specific. Multiple rules might reference different databases as one rule’s output might be an entity from a different database. Also, placing flow functions like splits, drip sequencing, time delay, or A/B pathing would be sooo hot.
Note: if you go down this route, I would love to help design this.
Automation Rules:
Fibery’s automation rules are generally solid, but I often hit limitations that slow development or force workarounds.
Key Limitations:
-
No “If / Else” logic — only “If.”
Flows would help address this gap. -
No reusable inputs/outputs between stages.
Only the first stage has defined inputs from the trigger. Because of this, temporary entity updates and multiple chained rules are often needed. Flows would solve this too, because outputs for the rule would be referenceable. -
Limited support for looping over multiple entities.
For example: “If X occurs, do Y for each linked entity.” You can update related entities, but not easily create new ones per linked record.This capability would be extremely helpful for:
- Building project & task template automations
- Supporting workflows such as ordering and fulfillment
Top Wishlist
If Fibery’s new automation system were integrated with a native email and SMS marketing tool (tracking opens, clicks, unsubscribes, etc.), I’d rarely need another CRM. Currently, Fibery’s email integration is functional but limited.
Other improvements I’d rank up here :
-
Context-based entity views - Add Views to Entities
-
Required fields at state change (not just creation) and other field validation - Conditional Required Fields - Workflow validation