# Append to Rich Text Fields of Linked Entities

**URL:** <https://community.fibery.io/t/append-to-rich-text-fields-of-linked-entities/8042>\
**Category:** Ideas & Features\
**Tags:** automations\
**Created:** [January 1, 2025, 6:39pm UTC](https://community.fibery.io/t/append-to-rich-text-fields-of-linked-entities/8042 "2025-01-01T18:39:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [January 1, 2025, 6:39pm UTC](https://community.fibery.io/t/append-to-rich-text-fields-of-linked-entities/8042/1 "2025-01-01T18:39:39Z")

</div>

I have a button that when pressed applies a template to my projects from the templates database.  
I want to create an automation that allows me to apply a template to an existing project. This means I cannot write over the Project description, but I do want to append content from the template to the Description field.  
[The update referenced here](https://community.fibery.io/t/done-append-rich-text-fields-in-update-action-in-automations/6724) only allows us to append content to the entity that triggered the automation. In my case, the project template.  
I want to append content to the description (rich text) in my Project database. The option is not listed here.

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

---

<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:** [January 2, 2025, 9:55am UTC](https://community.fibery.io/t/append-to-rich-text-fields-of-linked-entities/8042/2 "2025-01-02T09:55:12Z")

</div>

I suggest having a rule in the Project database, which can be triggered from a button/rule in the template database.  
e.g. checkbox = true is the rule trigger, and the automation in the template database sets it to true

Or perhaps it’s not essential that the rule is triggered from the template database?