# 🧐 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:** 1\
**Showing post:** 27

<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:** [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")

</div>

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.

---

_[View the full topic](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819)._
