# Add a notes section for each trigger action

**URL:** <https://community.tulip.co/t/add-a-notes-section-for-each-trigger-action/1501>\
**Category:** Product Suggestions\
**Created:** [December 28, 2020, 8:48pm UTC](https://community.tulip.co/t/add-a-notes-section-for-each-trigger-action/1501 "2020-12-28T20:48:27Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Peter.Hartnett](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@Peter.Hartnett](https://community.tulip.co/u/Peter.Hartnett)\
**Post date:** [December 29, 2020, 1:31pm UTC](https://community.tulip.co/t/add-a-notes-section-for-each-trigger-action/1501/3 "2020-12-29T13:31:26Z")

</div>

Hey Kevin,

I have heard about the separation of trigger logic from each individual trigger. I love this idea. I guess my ask would be in that future state where they are separate, add more ability to document.

1. I agree that the content pane is probably not the right place to have this information. We really want the comments tied to each of the actions the trigger does
2. We actively avoid 50 action single triggers for this very reason (along with some stability issues we have had). In my opinion, most triggers shouldn’t be more than 10 actions. _1 trigger does 1 thing_ has been our mentality when building app logic. If you have to say “and” while describing what it does, it should be separated.
3. UI wise, this is a little bit of a challenge. Ultimately in most cases I dont need a comment to understand why that line is required, its the 10% that I really need that feature and dont have it that are a pain. Here is what im thinking:  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/1X/25f5c49012c644c76d3a21f59d9740f8f12875ea.png)  
Not an impediment in those 90% of cases, but available in the other 10%

Thoughts?  
Peter

---

_[View the full topic](https://community.tulip.co/t/add-a-notes-section-for-each-trigger-action/1501)._