# Trigger an automation from Rich Text field

**URL:** <https://community.fibery.io/t/trigger-an-automation-from-rich-text-field/3653>\
**Category:** Ideas & Features\
**Tags:** automations\
**Created:** [December 5, 2022, 11:08am UTC](https://community.fibery.io/t/trigger-an-automation-from-rich-text-field/3653 "2022-12-05T11:08:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![julien.erny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/julien.erny/32/5833_2.png) [@julien.erny](https://community.fibery.io/u/julien.erny)\
**Post date:** [December 5, 2022, 11:08am UTC](https://community.fibery.io/t/trigger-an-automation-from-rich-text-field/3653/1 "2022-12-05T11:08:38Z")

</div>

I would love to be able to trigger an automation from a Rich Text field or a Document. It could be by embedding a button in the text but maybe more versatile would be the ability to trigger through a link. For instance, provide a link to the automation and you could then embed this link however you like in a Rich Text

---

<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:** [December 5, 2022, 11:19am UTC](https://community.fibery.io/t/trigger-an-automation-from-rich-text-field/3653/2 "2022-12-05T11:19:50Z")

</div>

It is possible to enable fields (including buttons) for a mentioned item, so in some ways you can already trigger automations from within rich text.  
 ![firefox_68WP3jIb7l](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/899a6a88c681931cd125bbe771f4b92ef4ea9a6c.gif)

---

<div class="post-metadata">

**Author:** ![julien.erny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/julien.erny/32/5833_2.png) [@julien.erny](https://community.fibery.io/u/julien.erny)\
**Post date:** [December 5, 2022, 12:43pm UTC](https://community.fibery.io/t/trigger-an-automation-from-rich-text-field/3653/3 "2022-12-05T12:43:47Z")

</div>

That’s a great workaround that I had not thought about, thanks.  
It could indeed work in some cases however it does not really cover the need as this setting is db-level. So if I’m writing a manual for example that says “in that case, click on this [button], in the other case, click on the [other button] it won’t work.”

---

<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:** [December 5, 2022, 12:48pm UTC](https://community.fibery.io/t/trigger-an-automation-from-rich-text-field/3653/4 "2022-12-05T12:48:18Z")

</div>

Depending on what you need to achieve, you could either:  
create some dummy entities that exist solely to hold the button automations you need, or  
create a linked database of entities, each of which represents an automation.

What are you exactly trying to achieve with your automations?

---

<div class="post-metadata">

**Author:** ![julien.erny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/julien.erny/32/5833_2.png) [@julien.erny](https://community.fibery.io/u/julien.erny)\
**Post date:** [December 6, 2022, 1:12pm UTC](https://community.fibery.io/t/trigger-an-automation-from-rich-text-field/3653/5 "2022-12-06T13:12:39Z")

</div>

Not sure how this would work…  
In short my use case is the following: I have an entity type (let’s call it E) that represents an observation/opportunity noticed by the user. This opportunity should trigger several possible actions depending on a workflow (if A do action\_A else if B do action\_B else do action\_C). This workflow is written in a Rich Text field of E (like a user manual of sort). At the moment, in the description, I say "if A then click on the button ‘Action\_A’ ". It’s actually working so it’s really no big deal. I was just slightly frustrated to not be able to just embed the ‘action\_A’ button in the manual.  
As far as I understood your advice, I could create an entity of type Action\_A (linked to E and whatever entities action\_A is creating) just to hold the automation, meaning a whole DB for one automation. That seems a bit overkill considering how bad I need this (meaning not so much 😅).  
I will keep your advice in mind though as I’m sure it will come in handy one day…

---

<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:** [December 6, 2022, 1:20pm UTC](https://community.fibery.io/t/trigger-an-automation-from-rich-text-field/3653/6 "2022-12-06T13:20:51Z")

</div>

OK, I see what you mean: the buttons already exist in the entity, available to be pressed, but putting them ‘inline’ with the instructions would reduce friction.

I think in the long-term, the number of things that are possible within rich text will increase (maybe buttons, maybe global formulas, maybe ‘transclusions’) but I don’t think they will be delivered in the short-term I’m afraid.
