# 🧐 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:** 20\
**Page:** 1

<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:** [October 15, 2025, 2:27pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/1 "2025-10-15T14:27:17Z")

</div>

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!

---

<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:** [October 15, 2025, 2:27pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/2 "2025-10-15T14:27:27Z")

</div>



---

<div class="post-metadata">

**Author:** ![mkervo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mkervo/32/11450_2.png) [@mkervo](https://community.fibery.io/u/mkervo)\
**Post date:** [October 15, 2025, 3:26pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/3 "2025-10-15T15:26:24Z")

</div>

Hello,  
The use case I can think of is “improved workflows” as discussed in this thread:

> [@Invitation to users wanting improved workflows](https://community.fibery.io/t/invitation-to-users-wanting-improved-workflows/3259):
>
> We know that the current workflow implementation is simplistic, and given that there are quite a few topics here that relate to workflows, e.g. …it seems like there are plenty users who would like more sophistication. Without making any promises, I would like to invite users to get in touch if they have specific use cases in mind that cannot currently be achieved in Fibery. This may allow us to develop templates that might be useful, as well as helping us understand what functions/features…

I think a lot of companies have complex workflows which mix automations, processes and manual procedures (tasks). It’s difficult to document the processes well and to mix both worlds (automation with human in the loop).

The most difficult thing is to follow each ongoing process execution. (e.g. a specific customer onboarding, a project lifecycle, a marketing campaign).

The alternatives are:

- Domain locked workflow solutions. A lot of Saas products propose workflow solutions
  - CRMs -e.g. [Projects by Pipedrive - Knowledge Base | Pipedrive](https://support.pipedrive.com/en/article/projects-by-pipedrive)).
  - Project Managment - [Introduction to Jira Workflows | Atlassian](https://www.atlassian.com/software/jira/guides/workflows/overview#relationship-between-workflow-and-board)

- Powerful workflow engines which lack end-user friendly interfaces
  - (e.g. [https://www.windmill.dev/](https://www.windmill.dev/), [https://temporal.io/](https://temporal.io/))

- And well.. N8N which is great. But it is not really ‘human in the loop’ friendly 🙂

In the end, it’s important for a company to track and improve the efficiency of its processes. It’s also important to quickly onboard on those.

EDIT:  
Maybe materializing Workflows, allowing to manage a set of rules and their correlations. Properly handling the “time / transition / contract” aspect of automation.

For an example. A task status can switch to ‘Done’ or ‘Canceled’ only when it is not ‘Draft’. And depending of the “completion” or “cancellation” event. It would trigger other rules, like Creating a ‘Report’ or a ‘Test’. To ‘cancel’ a task, maybe it should be mandatory to fill a ‘form’ with a proper reason.  
And you could see all this logic on a proper Workflow page.

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [October 15, 2025, 3:32pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/4 "2025-10-15T15:32:46Z")

</div>

Before responding, curious what you mean by “full re-write”, and what (from the feedback collected) justifies re-writting instead of adding missing features. What features would a re-write unlock?

1. 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).

The only time I’ve reached for scripts recently due to these limitations:  
[Unlink Automations to Reference Earlier Steps](https://community.fibery.io/t/unlink-automations-to-reference-earlier-steps/5132) and [To be able to use Formula in Automation filters](https://community.fibery.io/t/to-be-able-to-use-formula-in-automation-filters/3706)  
2. No  
3. Better data input (theme with several parts, hope it counts under a single thing:  
["Filters aren’t applied because they have missing ‘𝑥’ dynamic values"](https://community.fibery.io/t/filters-aren-t-applied-because-they-have-missing-dynamic-values/4560),  
[New Feed entity form should open as popup](https://community.fibery.io/t/new-feed-entity-form-should-open-as-popup/9232),  
[Allow using a Formula to define Default Values](https://community.fibery.io/t/allow-using-a-formula-to-define-default-values/1929), [What if entity view was treated as a dashboard?](https://community.fibery.io/t/what-if-entity-view-was-treated-as-a-dashboard/8322).

I personally think automations in Fibery are already much more powerful than most competing platforms. (The “Step 1 Linked Entity” is amazing for complex automations).  
Are there things that could be improved? Yes. Looping, conditions, using step results are examples. But the workarounds needed (at least for me) have not yet justified spending the time and energy into a full re-write of automations. Again, I’m curious to understand what features can’t be added without a full rewrite.

---

<div class="post-metadata">

**Author:** ![christamae](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/christamae/32/13729_2.png) [@christamae](https://community.fibery.io/u/christamae)\
**Post date:** [October 15, 2025, 3:53pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/5 "2025-10-15T15:53:59Z")

</div>

I’m still incredibly new to Fibery, but as far as I can tell, the ability to templatize a project plan seems limited. If I could allow my users to easily build their own templates that capture the multi-level Milestones, Taks, and Subtasks needed to complete the project, it would be game-changing.

Our current approach is pretty time consuming and fragile due to how we have to map/look up field values using the native rule builder. I haven’t attempted to build this process with Zapier (which I use for some other automations), but I imagine it would still be really time intensive to set up and manage our templates.

As a simple enhancement, it’d be a great start if I could just duplicate an action in the rule builder.

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [October 15, 2025, 5:31pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/6 "2025-10-15T17:31:03Z")

</div>

> [@christamae](#):
>
> I’m still incredibly new to Fibery, but as far as I can tell, the ability to templatize a project plan seems limited

This is possible! I explain it here: [https://youtu.be/7tfhG7pIgHA?si=GbLUeLJKhqsGo3q2&t=1545](https://youtu.be/7tfhG7pIgHA?si=GbLUeLJKhqsGo3q2&t=1545)

You can cascade this logic to as many levels as you’d like. The “When linked to entity” trigger is so so powerful, especialy when combined with lookups. Do pay attention to the correction in the comments of the video to reduce the number of automation runs.

---

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [October 15, 2025, 6:58pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/7 "2025-10-15T18:58:07Z")

</div>

[Webhook Action in Automations](https://community.fibery.io/t/webhook-action-in-automations/7485) would be my top request for automations. I can handle scripting, but I often just want the more quickly understandable layout of a GUI around webhooks (both during setup and reviewing later).

Other top automation wishlist items for me include [Ask user input for rules](https://community.fibery.io/t/ask-user-input-for-rules/2496), [Automatically linking with formulas](https://community.fibery.io/t/automatically-linking-with-formulas/5891), and [Enable file field to be a "where" filter in the action trigger of automations](https://community.fibery.io/t/enable-file-field-to-be-a-where-filter-in-the-action-trigger-of-automations/8366) (maybe more feasible after file field changes are complete)

My one feature request to rule them all is [More Flexible Date FIeld](https://community.fibery.io/t/more-flexible-date-field/2481). Without it, task management is just so much more cumbersome.

---

<div class="post-metadata">

**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\
**Post date:** [October 16, 2025, 5:28am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/8 "2025-10-16T05:28:05Z")

</div>

1. Working with both collection fields and non collection fields. (perhaps this is more of a formulas item, but this is usually the “simple” thing that I find myself wishing I could quickly do in automations)
2. No
3. More robust communications within Fibery. For example, publishing something like the Threads feature (I think I put all my thoughts on this in other posts).

---

<div class="post-metadata">

**Author:** ![timothy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/timothy/32/11812_2.png) [@timothy](https://community.fibery.io/u/timothy)\
**Post date:** [October 16, 2025, 3:01pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/9 "2025-10-16T15:01:31Z")

</div>

Super excited about upgrades to Automations!

1. What use cases you imagined with Fibery, but can’t do them because of poor automations?

- Address entities not linked to trigger entity – This is a BIG restriction. Example: I want to record a transaction for a specific Contact. From that Contact entity, I want to create a Journal entry. That Journal entry should always have at least 2 individual Line Item entities. Because those line items are not directly linked to the Contact entity, I can’t create them with a button on the Contact. Instead, I have to do one of 2 things: create an unnecessary relation between line items and Contact (this really confuses and complicates the data model) or try to 2-step the automation: create the Journal entry and then have a rule that creates the Line Items (which is much more fragile than a button where I can specific what exactly needs to be done in the context of the button).
- Loops – e.g., I need to create an entity that pairs a single person with a single project for each new project. I know I can do it with scripts, but a ‘for each’ automation is actually a pretty common use case. Scripts are a lot harder and so automations just end up not happening.
- Variables – this is one of the biggest things I miss from Notion’s automations. Being able to introduce a variable and then operate on it is very helpful in calculations, dynamic automations, etc. Scripts compensates for this, but there are lot of things I just put off automating or suffer with manual entry because scripts are a quantum leap in complexity and I don’t have the time to sit and write them.
- Conditional / case PER STEP – e.g., suppose I have an automation for a Project. If it’s a certain type of project, I want it to avoid creating one task or populate a given field differently. Right now, I have to do one of: a) script it (ugh - I just don’t do it then), b) multi-stage it with cascading rules (fragile because they are linked by conditions instead of directly – and the logic might fail unexpectedly), or c) set up a different automation for EACH different case (complicated and becomes a behemoth to maintain).

---

<div class="post-metadata">

**Author:** ![jandrabek](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jandrabek/32/10414_2.png) [@jandrabek](https://community.fibery.io/u/jandrabek)\
**Post date:** [October 16, 2025, 8:03pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/10 "2025-10-16T20:03:39Z")

</div>

For me the need is possibility to combine formula and manual input. The idea is that formula outputs value and I can modify it. When using formula only this is simple blackbox. Ability to alternate value is something I miss.

The reason behind it is that for me Fibery has the potential to be the best email client with relations and the whole system.

When I will be able to alter formula I can send emails.

---

<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:** [October 17, 2025, 5:34am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/11 "2025-10-17T05:34:55Z")

</div>

1. Desires:

- Button: When creating an entity I want to choose from the relevant/related entities only: ["Filters aren’t applied because they have missing ‘𝑥’ dynamic values"](https://community.fibery.io/t/filters-aren-t-applied-because-they-have-missing-dynamic-values/4560)

- UI-based way to create webhooks in Fibery.

- Chains of automations where the next steps could use the results of the previous steps.

- Chains of multi-layered If-Then-Else blocks in rules & buttons together with the flow visualization.

- Variables in rules & buttons.

- Workflows like in Jira in the way we could setup steps, rules & constraints.

- Multi-screen flows & visual (flow) progress indicator. I want a sales rep to quickly see what needs to be done, like Account \> Contact, i.e. Create Account, Create Contact. Or for an e-commerce order fulfillment process: Review Order Details \> Approve \> Create Fulfillment Order \> Pick & Pack \> Ship  
Examples: [https://youtu.be/oZ65kgmeie8?si=rqp9KCflZqdTJW\_9](https://youtu.be/oZ65kgmeie8?si=rqp9KCflZqdTJW_9)  
[https://youtu.be/LN4xvSFU-9Q?si=2JPyVjCjzgluUuXr](https://youtu.be/LN4xvSFU-9Q?si=2JPyVjCjzgluUuXr)

- Required fields not requiring me to pre-select a value like it is required now. I simply want a user not being able to submit the form unless they provide a value (like a required parameter in a standard html). Currently, I need to add rules to validate this simple fact & revert to the previous step which is counter intuitive.

- Full-featured Email - I’d love to use Fibery as my only email client and build sequences of tracked emails and other actions.

- Ability to select email template using rule or button based on a condition.

- Support for OpenRouter API (multiple AI models under a single umbrella).

- Execute client-side JavaScript or extend Fibery standard UI capabilities. This one is a big dream since this creates possibilities to extend Fibery standard UI features. There was a need of Jasper’s client to visualize a 3D object based on the object properties that are stored in Fibery. It would be awesome not to rely on creating the specific browser extensions.

1. No.

2. A “single” thing:

- 

> [@"Filters aren’t applied because they have missing ‘𝑥’ dynamic values"](https://community.fibery.io/t/filters-aren-t-applied-because-they-have-missing-dynamic-values/4560):
>
> Here is one place that I can’t use the dynamic relation filter: This is from a Button whose Action is “Link entities (Ask User)”, for a self-related M2M collection. The filter does remember its setting, which is great +1

- [Control display of Action button?](https://community.fibery.io/t/control-display-of-action-button/354)

- [Show/hide field based on formula](https://community.fibery.io/t/show-hide-field-based-on-formula/1499)

- Required fields not requiring me to pre-select a value like it is required now. I simply want a user not being able to submit the form unless they provide a value (like a required parameter in a standard html). Currently, I need to add rules to validate this simple fact & revert to the previous step which is counter intuitive.

- [Button: Customizing what fields to show in the dropdown for the related field](https://community.fibery.io/t/button-customizing-what-fields-to-show-in-the-dropdown-for-the-related-field/9837)

---

<div class="post-metadata">

**Author:** ![NicolSpies](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nicolspies/32/4317_2.png) [@NicolSpies](https://community.fibery.io/u/NicolSpies)\
**Post date:** [October 17, 2025, 7:53am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/12 "2025-10-17T07:53:03Z")

</div>

I needed to interface Fibery with WhatsApp for sending WhatsApp messages and documents from Fibery to customers and receiving WhatsApp messages from customers into Fibery.

The only way I could do it was to interface Fibery with Make (formerly Integromat) where the WhatsApp interfacing and automations were done in Make.

---

<div class="post-metadata">

**Author:** ![Hendrik](https://avatars.discourse-cdn.com/v4/letter/h/839c29/32.png) [@Hendrik](https://community.fibery.io/u/Hendrik)\
**Post date:** [October 17, 2025, 8:42am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/13 "2025-10-17T08:42:30Z")

</div>

PDF report designer  
(please)

---

<div class="post-metadata">

**Author:** ![Bachi2k](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bachi2k/32/1770_2.png) [@Bachi2k](https://community.fibery.io/u/Bachi2k)\
**Post date:** [October 17, 2025, 9:11am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/14 "2025-10-17T09:11:40Z")

</div>

Hi, I would like to see an option to convert an automation workflow to a script using the API.  
With this approach, you can start with the workflow, and when you are running out of options, you can switch to a scripting aproach and have full control.  
This will also lower to bar to use the scripting API, I assume.  
Just my 2 Cents Marc

---

<div class="post-metadata">

**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 17, 2025, 10:56am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/15 "2025-10-17T10:56:52Z")

</div>

Syncing two Select Fields is currently pure cancer.  
Let’s say I have 2 different select fields, both with the same number of items, but one might have longer texts and one shorter,  
for example

One might have a single select field option called:  
“High - critical features are not working or data loss imminent”  
the other might have a single select field called simply “High”.

Both of them have the same values, so I was expecting I could sync them by Value but nope, it’s not possible.

---

<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:** [October 17, 2025, 11:31am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/16 "2025-10-17T11:31:19Z")

</div>

> [@Mircea\_Braescu](#):
>
> Syncing two Select Fields

Are you talking about two select fields on the same db? If so, what’s the use case for two select fields, where they need to always stay in sync? Why is a single field not sufficient?

---

<div class="post-metadata">

**Author:** ![Tommy\_Hedley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/tommy_hedley/32/6468_2.png) [@Tommy\_Hedley](https://community.fibery.io/u/Tommy_Hedley)\
**Post date:** [October 17, 2025, 4:15pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/17 "2025-10-17T16:15:12Z")

</div>

1. I am inclined to agree with @RonMakesSystems , pretty much everything I want to do I can do with scripts. I could see that in the long term it makes sense to have the visual Automation system be as functional as scripts for non-technical users, but it seems like in the short term you could enable the most functionality by adding scripts back to the standard plan. That said, there are still a few specific improvements that would be helpful for me:
  1. Add a secret manager to the Automation system. I understand that putting API keys into automations if _fairly_ secure, it would be really nice to have all of your external API keys in a separate, secure place and call them by variable in scripts/automations.
  2. Add the ability to call Custom Integration Actions in scripts and send integration actions for batches of entities.

2. I currently use Make to sync some appointment entities to an external calendar, partly because of no secret manager and partly because the Google calendar API is annoying.
3. Polymorphic/multi-relations, I keep hoping to see these on the roadmap but I’m worried they’re gonna stay on the backburner. I frequently find myself working around not having these when trying to model all sorts of data and having to add extra, unnecessary fields to combine two distinct datatypes.

---

<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:** [October 18, 2025, 5:17am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/18 "2025-10-18T05:17:31Z")

</div>

My use of Fibery revolves around the great linking and referencing/backlinks, and I am yearing for that start to integrate thoroughly with the great commenting features for the ability to see disparate items around a business that are tracked in Fibery and how they relate, and generally just see more information at a glance without searching endlessly. Tying comments and references together would go a great length to solve this, so I’ll say one feature I’d like to see before further automation improvements is [For Activity Stream, ability to see in chronological order References & Comments](https://community.fibery.io/t/for-activity-stream-ability-to-see-in-chronological-order-references-comments/1300)

---

<div class="post-metadata">

**Author:** ![Eva\_Folch](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eva_folch/32/11814_2.png) [@Eva\_Folch](https://community.fibery.io/u/Eva_Folch)\
**Post date:** [October 18, 2025, 10:52am UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/19 "2025-10-18T10:52:47Z")

</div>

I’m not a coder, but I love using automation through simple tools like **buttons**. For example, in **Coda** , I can trigger a webhook directly from a button — this lets me send data like **invoices or expenses** straight to my accountant.

It would be amazing if Fibery buttons could do something similar — trigger a **webhook** or external action directly.

**Button Filters & Conditional Logic**

Having **filters or conditions** in buttons would make workflows much smarter.  
For example:

- When I create a **Quote or Invoice** , I’d like the system to automatically choose the **language** based on the client’s language (English vs. Spanish).

- I have a button that transforms a deal into a **Project entity** , but depending on the client type, I need different behaviors (some require line items, others don’t), Currency Symbols are different depending on the client as well…  
A conditional filter or logic in buttons would make this much simpler.

#### Formula-Based Filters & Colors

It would be super helpful to use **formulas** in entity filters or color rules.  
For example:

- Color an entity **red** or filter, if the **bank amount doesn’t match the invoice total minus expenses**.  
This would reduce the number of extra calculated fields I currently need.

#### Smarter Lookup & Relation Filtering

When linking entities, it would be great to:

- Filter lookup options dynamically, ex… by **Client Name** from the current entity.

- Filter by specific date parts, like `date.year`, when selecting related items.

So, yeah! Better automations would be my first request! Otherwise, instead, I would love more freedom in the way that the Fields are organized/look inside an Entity. To be able to have fields next to each other so you don’t need to scroll down so much. (Column Style)

---

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

</div>

> [@Eva\_Folch](#):
>
> it would be great to:
> 
> - Filter lookup options dynamically, ex… by **Client Name** from the current entity

Is this not covered by [this](https://the.fibery.io/@public/User_Guide/Guide/Relation-Filters-and-Sorts-177/anchor=Using-dynamic-values--63cb8e1d-2c01-4760-9a72-bef50ec94838)?

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