# šŸ§ Your opinion needed. Automations in Fibery (limitations and opportunities) **URL:** \ **Category:** News & Announcements\ **Created:** [October 15, 2025, 2:27pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819 "2025-10-15T14:27:17Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![julien.erny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/julien.erny/32/5833_2.png) [@julien.erny](https://community.fibery.io/u/julien.erny)\ **Post date:** [October 18, 2025, 12:34pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/21 "2025-10-18T12:34:35Z")
1. The ability to union lists of the same type is hands on the first on my list. But using formula in filters and sorts would a close second. A more evolved language allowing loops and variables would also be fantastic. Like a simple scripting language that would allow to open it to more users without causing too much security issues. 2. Iā€™m using an external workflow but not sure itā€™s due to lack in automation. Iā€™ve created a shortcut to send ā€œbrain dumpā€ kind of inputs without getting out of my workflow (i.e from anywhere on my computer or my phone) to be reviewed on Fibery later (GTD-style inbox) 3. Canā€™t think of anything really ---
**Author:** ![jurgenappelo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jurgenappelo/32/11935_2.png) [@jurgenappelo](https://community.fibery.io/u/jurgenappelo)\ **Post date:** [October 18, 2025, 5:15pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/22 "2025-10-18T17:15:09Z")
I use Make extensively. Please donā€™t try to build a weak copy of Make or n8n. Those tools already exist. Leave the generic automation (like integrations with other tools) to them. Whatā€™s the benefit of being able to send a message to Slack directly from Fibery? Sure, it saves me one credit in Make. Big deal. The Make scenarios are much more advanced than the Fibery rules. Letā€™s keep it that way. Instead, focus on what is _specific_ to Fibery: automations that trigger on any kind of change in the data or data structures. Iā€™d like to trigger a rule when a field is added to a database. Or when a view of a database is changed. Or when the number of entities in a database exceeds a certain number. Etc. And Iā€™d like more complex flows in the rules, like if statements and switches. The workarounds that I have now to achieve conditional flow make everything quite hard to follow. The single most important thing for me in Fibery for me is maintenance features on data structures: how is which field used and where? The flexibility in Fibery is awesome but, because of the many changes in the structures, the data models easily end up with fields, formulas and relations that arenā€™t being used anymore. I have no idea how I can get insight on that. I want Fibery to tell me which parts of the data structures serve no purpose anymore. ---
**Author:** ![lars](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lars/32/7322_2.png) [@lars](https://community.fibery.io/u/lars)\ **Post date:** [October 18, 2025, 6:50pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/23 "2025-10-18T18:50:24Z")
For me, the most annoying limitations of automations (not counting JavaScript actions) are as follows: - No conditional actions (sometimes conditions cannot be fully expressed as rule filters) - No loops, hard to do any actions on _some_ related items (for example, it is basically impossible to create ā€œradio buttonā€ checkboxes on a list of items without resorting to buttons or scripting; or from query result create new linked entities in a loop) - Also no iterating over formula results. Example use case: have a comma-separated list of e-mail-addresses in one field (from outside system, for example), link corresponding users to entity. - For button automations: Better feedback to the user, i.e. positive or negative messages displayed, maybe even asking for input in between steps. Currently, you need to resort to scripting for user feedback (by throwing errors for example) And sometimes, even automations are a necessary workaround because formulas are not mighty enought: I would love to dynamically query objects in a formula that have no existing relation to the entity the formula is computed on. If I had to pick a single thing that is more important than the automation improvements, I would agree with @mkervo and choose ā€œbetter workflowsā€ (stricter state and transition handling, enforce comment/entity change on state transition, better forms with default values, etc.) ā€“ and I actually feel that this is more important than a rewrite of automations, because scripting ā€“ while tedious and annoying ā€“ does already work around the limitations listed above quite well. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 18, 2025, 6:55pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/24 "2025-10-18T18:55:15Z")
> [@Tommy\_Hedley](#): > > Polymorphic/multi-relations, I keep hoping to see these on the roadmap but Iā€™m worried theyā€™re gonna stay on the backburner. In plans for next year actually, but canā€™t promise anything yet. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 18, 2025, 6:55pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/25 "2025-10-18T18:55:39Z")
Fantastic feedback so far, folks, very helpful! ---
**Author:** ![Sev](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@Sev](https://community.fibery.io/u/Sev)\ **Post date:** [October 20, 2025, 10:34am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/26 "2025-10-20T10:34:28Z")
I have to agree with the message below. I apologise if my answer seems off-topic, but given that the scripts in automations cover a vast number of use cases, I see **improvements in the formula field** (maybe even allowing JS in them) as a more impactful feature, because I have seen several formula-shortcoming workarounds in the forum that cause the use of automations instead. As for automations, between the super-powerful scripting in Fibery, and external tools like pipedream, I cannot imagine running into serious shortcomings. > [@RonMakesSystems](#): > > Nothing. If the no-code canā€™t do it. We can script. Anything is possible there. I think this topic is relevant for this discussion: [šŸ‘‚ Feedback needed: scripts in automations that shouldnā€™t be scripts](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560). ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [October 20, 2025, 1:47pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/27 "2025-10-20T13:47:53Z")
1. What use cases you imagined with Fibery, but canā€™t do them because of poor automations? 2. Do you compensate that with n8n, API, Make, Zapier or other external tools? 3. What a **single** thing more important for you to have in Fibery instead of better automations? Please do not provide many, just one šŸ™‚ - Viewer context - so Entity Views know which users are viewing the enity. I have a [chrome extension](https://community.fibery.io/t/prototype-chrome-extension-to-facilitate-viewer-context/5816) of that, but should be out of the box. Massive benefits. ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [October 20, 2025, 1:55pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/28 "2025-10-20T13:55:58Z")
Related idea about Automations > [@Automation management using databases + Prompt to create script comment](https://community.fibery.io/t/automation-management-using-databases-prompt-to-create-script-comment/8829): > > Automations in Fibery I find currently ā€˜underdevelopedā€™ in that management of automations and scripts is not easy. Seen the focus on AI and workflows, this becomes even a greater need, so its likely that at some point this will be improved. In the meantime I have the following solution: Automation & Script management using databases Scripts in Fibery are dependent on the correct automation setup. This is how I manage that: ā€˜Automationā€™ database (with rich text field describing the automationā€¦ ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [October 20, 2025, 2:02pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/29 "2025-10-20T14:02:30Z")
Related also > [@Improving AI Workflow Tools in Fibery](https://community.fibery.io/t/improving-ai-workflow-tools-in-fibery/7964/3): > > I canā€™t help but continue to dream how powerful AI Agents & Workflows could level up Fibery 1,000x. In hope of some community feedback or further collaboration, Iā€™m sharing some initial progress Iā€™ve made while tinkering with implementing an Agentic Workflow workspace in Fibery, albeit with all of its limitations. Iā€™ve published [this public Fibery whiteboard](https://maas.fibery.io/AI_Agent_Workspace/Fibery-Agent-Framework-1070?sharing-key=4b016761-2066-4ad7-833d-c01b98f40ab3) with my current thought process and concept progress. KEY CONCEPā€¦ ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [October 21, 2025, 10:48am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/30 "2025-10-21T10:48:42Z")
What would be really useful is also having shared functions across formula fields. That would allow to overcome current UI-level limitations of presenting data while not requiring creating redundant formula-level piece of functionality over and over like this one: ```auto ToText(Year(Deadline)) + If( Month(Deadline) < 10, "0" + ToText(Month(Deadline)), ToText(Month(Deadline)) ) + If(Day(Deadline) < 10, "0" + ToText(Day(Deadline)), ToText(Day(Deadline))) ``` just to show date with leading zeros. ---
**Author:** ![Sev](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@Sev](https://community.fibery.io/u/Sev)\ **Post date:** [October 21, 2025, 11:38am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/31 "2025-10-21T11:38:58Z")
> [@myg\_ge](#): > > What would be really useful is also having shared functions across formula fields. Agreed. To avoid getting further off-topic, I have found a handful of somewhat-related topics, but the closest one is this: [Variables in formulas](https://community.fibery.io/t/variables-in-formulas/1277). I am moving my response there šŸ™‚. ---
**Author:** ![Sppam\_Kontrol](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sppam_kontrol/32/12112_2.png) [@Sppam\_Kontrol](https://community.fibery.io/u/Sppam_Kontrol)\ **Post date:** [October 22, 2025, 5:41am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/32 "2025-10-22T05:41:13Z")
we have issue with the amount of automation allowed per plan. it is too limiting. 1. Imagine, you just want to move one doc to another in a self-relation. It is already counted as 1 automation. 2. So, there is no notification truly embedded in the platform. Just creating a notification already eats up credits using the automation as well. 3. there is also a lack of support for automation with the docs. we would like to do automation on exporting docs and/or entries to a pdf where the pdf structure/page properties are also configurable. ZUsing JS alone is not practical as we have to reconfigure all the codes again even with just a small changes from the sources. 4. Request for a scheduler management for automation. these includes remaining credit, predictive utilization, manage schedules, create cascading automations (like after 1 automation is done, it can perform the next one) this is to create a better management of chunks of automation in a intended automation pipeline. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [October 22, 2025, 6:06am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/33 "2025-10-22T06:06:52Z")
> [@Sppam\_Kontrol](#): > > Imagine, you just want to move one doc to another in a self-relation. It is already counted as 1 automation. Not sure what you mean here. I guess youā€™re not talking about [documents](https://the.fibery.io/@public/User_Guide/Guide/Documents-85) given that youā€™re referring to self-relations. Why would changing how entities are linked via a self-relation count as an automation? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 22, 2025, 6:12am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/34 "2025-10-22T06:12:07Z")
---
**Author:** ![Sppam\_Kontrol](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sppam_kontrol/32/12112_2.png) [@Sppam\_Kontrol](https://community.fibery.io/u/Sppam_Kontrol)\ **Post date:** [October 22, 2025, 6:18am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/35 "2025-10-22T06:18:35Z")
Similar to the template for the [the.fibery.io](http://the.fibery.io), under the DBā€™s Rules, there is propagate section to children and section change to children. those are 2 rules. And everytime we just move the subdoc to a different doc category. it is already treated as an activity. Our opinion in case is just a example where similar small items such as these ones eat alot of automation credits especially if there are a good amount of there applied across similar dbs. ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [October 22, 2025, 2:18pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/36 "2025-10-22T14:18:51Z")
> [@mdubakov](#): > > What a **single** thing more important for you to have in Fibery instead of better automations? Improved complexity with collections in formulas (or computed lookups). Iā€™d like to directly calculate filtered lookups without needing helper fields/calculations, to control the sort order, and specify the number of results. To me, this is preferrable to the planned collection view update to lookup fields > [@Allow Formulas to return a collection of just a specific field from Filter results](https://community.fibery.io/t/allow-formulas-to-return-a-collection-of-just-a-specific-field-from-filter-results/5658): > > I have a Collection of ā€œRolesā€, where each Role is related to a User. I want to create a Formula field that returns the collection of all the Users linked to the Roles in the collection. But itā€™s not currently possible to return a collection of a particular field from the Filter results: Currently we can only do this kind of operation for a single result, not for all items in a collection: IIUC this can currently only be done by using a pair of Rules (Role Linked and Roleā€¦ ---
**Author:** ![Sppam\_Kontrol](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sppam_kontrol/32/12112_2.png) [@Sppam\_Kontrol](https://community.fibery.io/u/Sppam_Kontrol)\ **Post date:** [October 22, 2025, 8:31pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/37 "2025-10-22T20:31:22Z")
Also, I think that automation credits should be increase. Image just for the hiring team, even when sending a rejection email that takes a 1 rule in automation. Imagine for just 1 role, we have like 150-200 applicants, that already eat 1 user seat automation allocation in just a few days. It would be nice to have like a separate automation usage for like internal to the process of fibery vs external to fibery. there are automation internally that are just common features for some apps like notifications and we have to put automation just to have it. ---
**Author:** ![Fernando\_Fontoura](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/fernando_fontoura/32/12060_2.png) [@Fernando\_Fontoura](https://community.fibery.io/u/Fernando_Fontoura)\ **Post date:** [October 22, 2025, 8:43pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/38 "2025-10-22T20:43:18Z")
Alternatively or concurrently, extra credits to purchase would also help ---
**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\ **Post date:** [October 23, 2025, 2:27pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/39 "2025-10-23T14:27:35Z")
Both cases an example for the same DB is exactly the one I mentioned. I might want a ā€œreport issue formā€ where the priority text is ā€œHigh - critical features are not working or data loss imminentā€ā€ while for the devs on the receiving end, I want a compact view where they only see ā€œHighā€ in the Priority column. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [October 23, 2025, 2:47pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/40 "2025-10-23T14:47:07Z")
> [@Mircea\_Braescu](#): > > I might want a ā€œreport issue formā€ where the priority text is > ā€œHigh - critical features are not working or data loss imminentā€ā€ > while for the devs on the receiving end, I want a compact view where they only see > ā€œHighā€ in the Priority column. You could have a priority select field, where the Name is High, and then add a Text field to the select options, where the value for High would be ā€œCritical features are not working or data loss imminentā€. Then the issue is that form view does not currently allow for showing additional fields in the dropdown, right? Assuming that were fixed\*, is there any reason for having two identical select fields on the main db? \*Related topics: > [@Link or Create window, display other fields (besides ā€œNameā€) for easy identification of desired entity](https://community.fibery.io/t/display-fields-in-link-or-create-window/5679): > > I have many things in a single database that are all named the same. For example, in my ā€œIterationā€ database I already have over 200 records called ā€œIteration 1ā€ and there will ultimately be thousands more named the same way in the future. I wish that when I clicked on ā€œLink or createā€, I would be able to view some fields (like ā€œClientā€ or ā€œDue Dateā€ or ā€œTeamā€ for example) that are on the entity Iā€™m trying to link to. Currently the only fields that are shown are ā€œNameā€ and ā€œIDā€ and ā€œDatabaseā€ā€¦ > [@Open larger view on relation field dropdown](https://community.fibery.io/t/open-larger-view-on-relation-field-dropdown/8304): > > Problem: When choosing an entity to relate to, you might have many to choose from and not sure which on is that you are looking for. Either because of duplicate names, or just because you need to explore a little before choosing the right one. Right now I need to go a seperate view, explore / filter / search, find the one i need, go back to the original entity and link it or link it from the target entity, then go back to the original to make the rest of theā€¦ [Previous page](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819.md?page=1) [Next page](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819.md?page=3)