# Rich text to Markdown with relations in automation

**URL:** <https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289>\
**Category:** Ideas & Features\
**Tags:** automations, rich-text\
**Created:** [February 19, 2025, 11:14pm UTC](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289 "2025-02-19T23:14:54Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [February 19, 2025, 11:14pm UTC](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289/1 "2025-02-19T23:14:54Z")

</div>

I want to make a rich text field for templating, instead of doing this in the automations section. So the ability to reference fields in the rich text field with {{}}, and then in the markdown section in the automation, just reference {{Rich text field}}.  
Essentially allow nested markdown templates. This would allow for more user friendly templating. Can this be done with some scripting maybe?

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [February 20, 2025, 12:14am UTC](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289/2 "2025-02-20T00:14:55Z")

</div>

You would need one RTF to define the template, and a second “output” RTF field to hold the interpolated result, plus a Rule that triggers when any of the referenced fields are updated, and calculates a new result value and saves it to the “output” RTF.

---

<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:** [February 20, 2025, 7:27am UTC](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289/3 "2025-02-20T07:27:39Z")

</div>

If I understand the request correctly, I think it is not possible.  
An automation does one level of processing of the markdown at the time of execution.  
If you were to type `{{Rich text field}}` in the automation, then it would (correctly) interpret that as you wanting the contents of the Rich text field.  
If the Rich text field itself contained markdown expressions, e.g.  
`I would like to show {{This field}}`  
this will not be processed.

And I should also point out that rich text is stored as markdown, so what gets rendered as  
`I would like to show {{This field}}`  
is stored internally as  
`I would like to show \{\{This field\}\}`  
so it wouldn’t even work if there were multiple levels of markdown processing.

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [February 20, 2025, 9:14am UTC](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289/4 "2025-02-20T09:14:48Z")

</div>

I see, I’ll give Matt’s idea a shot… But yeah you’re getting the idea right Chris.

I guess this relates to the popular request of having in-line fields in RTF. But then having those fields dynamic…

Anyhow, I’ll leave this here as an idea. I get why it’s not possible at the moment (very easily), but I think it could be quite valuable when templating. (Which is something relevant across many domains).

---

<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:** [February 20, 2025, 11:59am UTC](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289/5 "2025-02-20T11:59:27Z")

</div>

When you can see consistent benefit of nested markdown templates in your workflows, then you can create a ‘Placeholder’ database that defines a string to be replaced through an automation, with a field Delimiters, the specific characters or sequences (like `[]` or `[[]]`) used to mark the beginning and end of a placeholder. An automation 'If RTF changes, replace Placeholders X with … and Y with …etc. Essentially its a templating engine based on automations. This combined with fibery markdown templates will allow for custom and dynamic nestings (e.g. replacement of embedded nodes in real time).

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [February 20, 2025, 12:13pm UTC](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289/6 "2025-02-20T12:13:27Z")

</div>

Ooh thanks Yuri!

I’ll give this a shot!

---

<div class="post-metadata">

**Author:** ![Tom](https://avatars.discourse-cdn.com/v4/letter/t/3d9bf3/32.png) [@Tom](https://community.fibery.io/u/Tom)\
**Post date:** [March 27, 2025, 1:09pm UTC](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289/7 "2025-03-27T13:09:30Z")

</div>

Did this work for you @RonMakesSystems ?  
And if so, would you be able to share a example  
Best regards

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [March 27, 2025, 7:37pm UTC](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289/8 "2025-03-27T19:37:26Z")

</div>

Hey Tom! No, I never got around to making this unfortunately.
