# Trigger Rules in Buttons as an Action / Vice Versa

**URL:** <https://community.fibery.io/t/trigger-rules-in-buttons-as-an-action-vice-versa/10069>\
**Category:** Ideas & Features\
**Created:** [November 21, 2025, 6:10pm UTC](https://community.fibery.io/t/trigger-rules-in-buttons-as-an-action-vice-versa/10069 "2025-11-21T18:10:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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 21, 2025, 8:08pm UTC](https://community.fibery.io/t/trigger-rules-in-buttons-as-an-action-vice-versa/10069/4 "2025-11-21T20:08:09Z")

</div>

> [@Click Action Buttons with an Action Button?](https://community.fibery.io/t/click-action-buttons-with-an-action-button/1170):
>
> Just for the sake of logic organisation (and not having the same code in several places) – is it possible to “click” an Action Button from the script of another Action Button? Call it like a method? Since it is created like a field, I figured it should also be accessible from the script like one? Simple use case: suppose both tasks and subtasks have an “Assign to me” button. By clicking “Assign to me” on a task can I auto-click “Assign to me” on every connected subtask? If yes, please help me …

I think this would solve it (your automation could ‘press’ the button).  
If you use the network inspector, you can probably reverse engineer the (unofficial and not guaranteed to remain stable) API call that causes a button to be pressed 😉

---

_[View the full topic](https://community.fibery.io/t/trigger-rules-in-buttons-as-an-action-vice-versa/10069)._