# 🧐 Your opinion needed. Automations in Fibery (limitations and opportunities)

**URL:** <https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819>\
**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:** 19\
**Page:** 4

<div class="post-metadata">

**Author:** ![danielbmarsh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/danielbmarsh/32/13104_2.png) [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)\
**Post date:** [October 28, 2025, 7:16pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/61 "2025-10-28T19:16:47Z")

</div>

@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.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f63c9f10b148166a64d4f873b96498d84ed8077a.jpeg)

**Automation Rules:**  
Fibery’s automation rules are generally solid, but I often hit limitations that slow development or force workarounds.

**Key Limitations:**

1. **No “If / Else” logic** — only “If.”  
Flows would help address this gap.

2. **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.

3. **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.

**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](https://community.fibery.io/t/add-views-to-entities/8986)

- **Required fields at state change** (not just creation) and other field validation - [Conditional Required Fields - Workflow validation](https://community.fibery.io/t/conditional-required-fields-workflow-validation/9268)

---

<div class="post-metadata">

**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\
**Post date:** [October 31, 2025, 7:39pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/62 "2025-10-31T19:39:46Z")

</div>

> [@mdubakov](#):
>
> We’ve accumulated a lot of feedback about Automations in Fibery and thinking about full re-write of this area. It is not an easy project. Here are some things we want to hear from you that may help us to make a decision:
> 
> 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 🙂
> 
> Thank you!

So, as promised I would respond to this topic. Here’s my thoughts after using automations a lot for the last weeks for generating PDFs.

1. Generating PDFs is cool but the use of it is limited because I can’t shrink images and I end up with huge PDFs. That is the most painful thing still as I have shared and I won’t repeat more than I have (until now). On the bright side, I really like the ability to HTML + CSS + JavaScript to make PDFs. And the Fibery AI also makes this more accessible.
2. I am working on compensating my pain with n8n 💊 I think it’s great that I use that now with Fibery.
3. Good question. A hard one because I find better automations very important. But it is not critical because n8n. You probably expect me to answer “better maps” but that is not it 😉 Perhaps a Fibery managed n8n environment? So users who are non-technical can just go there if they want more scripting? Can be an addition to the price or people can get monthly credits.

Have a good weekend y’all!

---

<div class="post-metadata">

**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\
**Post date:** [November 1, 2025, 10:40pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/63 "2025-11-01T22:40:01Z")

</div>

> [@mdubakov](#):
>
> - What use cases you imagined with Fibery, but can’t do them because of poor automations?
> - Do you compensate that with n8n, API, Make, Zapier or other external tools?
> - What a **single** thing more important for you to have in Fibery instead of better automations? Please do not provide many, just one 🙂

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?

- No.

1. What a **single** thing more important for you to have in Fibery instead of better automations? Please do not provide many, just one 🙂

- Integration with Salesforce _(Sync any object records, two way sync)_.

---

<div class="post-metadata">

**Author:** ![Lee\_Denny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lee_denny/32/8158_2.png) [@Lee\_Denny](https://community.fibery.io/u/Lee_Denny)\
**Post date:** [November 2, 2025, 10:28am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/64 "2025-11-02T10:28:06Z")

</div>

**Catch Webhooks**

We use scripts in fibery to make API calls and trigger events in other software without the use of Zapier, but we have to use Zapier to catch webhooks from them. Would like to be able to catch hooks directly in fibery and use the information to automate things.

**AI Interaction With Files**

We currently have to send files out to Zapier to use AI to review them, then bring the responses back.

**OCR On Files**

We currently have to send files out to Zapier to use OCR to extract data from them, then bring the responses back.

**Looping**

When we have a form response with multiple items we use looping in zapier to create a fibery entity for each item. Having the concept of looping in fibery automations might be useful.

**Branching**

Zapier supports pathways which we find useful and might be worth you looking at including in Fibery instead of just the yes/no filter and single pathway you currently have.

**Forms**

We rely a lot on forms to run our business. At the moment we have to use Gravity or Cognito Forms and build Zapier connections to get that information into fibery. Our number 1 feature to work on ahead of automations would be to make fibery forms good so we can just use those!

---

<div class="post-metadata">

**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\
**Post date:** [November 2, 2025, 10:55pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/65 "2025-11-02T22:55:35Z")

</div>

> [@mdubakov](#):
>
> 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 🙂

1. I can’t check the person who triggered the rule before it is triggered. “Add Filter for Entity” doesn’t allow “Where User is [function]”. A use case is “a field is updated, but what happens next depends on who updated it”—super important for true workflows.
2. No. I will though if there is not a native solution.
3. Branching and conditions—internal logic (if then else) and button display rules. You said one thing, but these are so entwined it’s not funny.

---

<div class="post-metadata">

**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:** [November 5, 2025, 1:07pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/66 "2025-11-05T13:07:00Z")

</div>

I shared my feedback already. But just want to emphasize how annoying and limiting is the following thing - I’d give up everything I wrote for you to fix this one:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/355ed0aa90d935ba276ea508ac8ce6a172b7a477.png)

---

<div class="post-metadata">

**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:** [November 5, 2025, 5:57pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/67 "2025-11-05T17:57:01Z")

</div>

Hi. There are suggestion about improving fibery. We want to know if what is the library/engine fibery use for its formula. Like are they using “Hyperformula”? At least we wish to share what features to add and make less friction to the dev team in case they want to add some of our ideas in the product roadmap.

---

<div class="post-metadata">

**Author:** ![Sergey\_Truhtanov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sergey_truhtanov/32/13986_2.png) [@Sergey\_Truhtanov](https://community.fibery.io/u/Sergey_Truhtanov)\
**Post date:** [November 6, 2025, 8:20am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/68 "2025-11-06T08:20:02Z")

</div>

Hi.

Our Formulas language and calculation implementation are not using any library/engine, it’s our in house implementation.

---

<div class="post-metadata">

**Author:** ![Jean\_Jordaan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jean_jordaan/32/6922_2.png) [@Jean\_Jordaan](https://community.fibery.io/u/Jean_Jordaan)\
**Post date:** [November 6, 2025, 10:59am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/69 "2025-11-06T10:59:11Z")

</div>

I wish SaaS apps did not invent their own formula/expression or workflow engines.

It’s less friction in the short term, but becomes a massive time sink as the system and usage matures.

It feels like it should be possible to build on general frameworks like Jinja/Nunjucks for expressions or [xstate](https://github.com/statelyai/xstate)/[bpmn](https://bpmn.io/) for workflows. It would still be a ton of work of course but at a higher level of abstraction hopefully.

---

<div class="post-metadata">

**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:** [November 6, 2025, 11:02am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/70 "2025-11-06T11:02:21Z")

</div>

> [@Jean\_Jordaan](#):
>
> I wish SaaS apps did not invent their own formula/expression or workflow engines.

Unfortunately it will never happen. Well, maybe in 20 years when it will not be needed at all and all work will done via API calls between AI Agents. Otherwise, all vendors will keep building own UI Views, own backend solutions, own DSLs

---

<div class="post-metadata">

**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:** [November 7, 2025, 12:06pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/71 "2025-11-07T12:06:23Z")

</div>

> [@October 23, 2025 / sauropod Multiple Files Fields per Database and some unexpected improvements](https://community.fibery.io/t/october-23-2025-multiple-files-fields-per-database-and-some-unexpected-improvements/9871/33):
>
> @mdubakov a great release, as always, thank you! I see Fibery is maturing and starting to support larger organizations bit by bit. From a high strategy perspectice, I think that Fibery has the characteristic to be a collective intelligence platform that allows AI and humans to analyze and orchestrate systemic organizational strategy. Not many users point to this potential because they use Fibery to solve operational challenges. But the real potential I see is not in operations only, its actual…

---

<div class="post-metadata">

**Author:** ![Lee\_Denny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lee_denny/32/8158_2.png) [@Lee\_Denny](https://community.fibery.io/u/Lee_Denny)\
**Post date:** [November 7, 2025, 3:01pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/72 "2025-11-07T15:01:10Z")

</div>

Could 2-way google calendar sync be part of automations? It is badly needed by our team and is provided by most fibery competitors as standard.

---

<div class="post-metadata">

**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:** [November 7, 2025, 3:57pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/73 "2025-11-07T15:57:21Z")

</div>

> [@Lee\_Denny](#):
>
> Could 2-way google calendar sync be part of automations?

It’s theoretically possible that we could add ‘external actions’ that allow you to create automations which push information from Fibery to Google Calendar, but fundamentally, this is not the same as true two-way sync.  
With two-way sync, there needs to be functionality to take care of conflict resolution, e.g. someone changes the calendar entry in Fibery and another person makes changes to the corresponding entry in GCal. If a Fibery automation pushed changes to GCal, it could end up clobbering the changes already made in GCal.  
2-way sync is hard ☹

---

<div class="post-metadata">

**Author:** ![Lee\_Denny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lee_denny/32/8158_2.png) [@Lee\_Denny](https://community.fibery.io/u/Lee_Denny)\
**Post date:** [November 7, 2025, 6:08pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/74 "2025-11-07T18:08:37Z")

</div>

A one way sync action from fibery to google calendar would be a really useful first step!

---

<div class="post-metadata">

**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:** [November 18, 2025, 1:23pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/75 "2025-11-18T13:23:17Z")

</div>

related

[Conditions in Buttons - Ideas & Features / Automations - Fibery.io Community](https://community.fibery.io/t/conditions-in-buttons/2621)

---

<div class="post-metadata">

**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:** [February 12, 2026, 3:16pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/76 "2026-02-12T15:16:54Z")

</div>

> [@Jonathan1](#):
>
> Be able to use the old value of a field when a trigger happen.

Now you can do it

> [@spouting\_whale February 12, 2026 / Fibery AI Context, Create and Update Reports with AI, tons of other improvements](https://community.fibery.io/t/february-12-2026-fibery-ai-context-create-and-update-reports-with-ai-tons-of-other-improvements/10385):
>
> Today’s release contains two dozens features from various areas, so anyone will find something to enjoy (we hope)! Our small AI team was especially productive recently (maybe because they know how to use AI tools better thinking). mage Fibery AI Context Working with AI in Fibery used to mean typing everything into a blank chat and hoping the assistant guessed what you were talking about. You had to remember exact names of Databases, Views, Rules, and Reports, and then carefully describe the…

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [March 24, 2026, 3:01am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/77 "2026-03-24T03:01:18Z")

</div>

Sorry I posted over [Here](https://community.fibery.io/t/automatically-move-dates-on-related-entities/10630) a use case I have around automations, hope it’s helpful to this topic!

---

<div class="post-metadata">

**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:** [May 21, 2026, 2:01pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/78 "2026-05-21T14:01:09Z")

</div>

> [@Jonathan1](#):
>
> Be able to have a Webhook to send messages to Google Chat.

released today [May 21, 2026 / Manage users visibility, Send web request action in automations](https://community.fibery.io/t/may-21-2026-manage-users-visibility-send-web-request-action-in-automations/10894)

---

<div class="post-metadata">

**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:** [May 21, 2026, 2:01pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/79 "2026-05-21T14:01:25Z")

</div>

> [@Eva\_Folch](#):
>
> It would be amazing if Fibery buttons could do something similar — trigger a **webhook** or external action directly.

released today [May 21, 2026 / Manage users visibility, Send web request action in automations](https://community.fibery.io/t/may-21-2026-manage-users-visibility-send-web-request-action-in-automations/10894)

[Previous page](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819.md?page=3)
