# Embed a View in a Rich Text field with an Automation? **URL:** \ **Category:** Get Help\ **Created:** [July 15, 2025, 4:40pm UTC](https://community.fibery.io/t/embed-a-view-in-a-rich-text-field-with-an-automation/9210 "2025-07-15T16:40:54Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Jonathan](https://avatars.discourse-cdn.com/v4/letter/j/aeb1de/32.png) [@Jonathan](https://community.fibery.io/u/Jonathan)\ **Post date:** [July 15, 2025, 4:40pm UTC](https://community.fibery.io/t/embed-a-view-in-a-rich-text-field-with-an-automation/9210/1 "2025-07-15T16:40:54Z")
I’m trying to create an automation that embeds a view inside a rich text field of an entity when it executes. I think I am to use the “Prepend (or Append) content to Field” Action. If I use the conventional way to create a link like this: View Name I can generate a link to the View (though it’s oddly not clickable—it just displays the URL, and I have to right-click and ‘open in a new browser tab’), but that’s not really helpful. I’d really like to have the view embedded so I can interact with it right there in the rich text field. There’s no info on how to embed a view via an automation action. Can I do this? Maybe via a markdown template? The guide says to mention an entity, I’d use this construction: [[#^DB\_ID/ENTITY\_ID]]. Just to see what would happen, I extracted the UUID of my view, and I tried using that in the Action like this: [[#^UUID]] and it prepended something called “unknown” into my rich text field. So it obviously didn’t find my View (and I think a mention is not really the same as an embed anyway). Any ideas? ---
**Author:** ![Jonathan](https://avatars.discourse-cdn.com/v4/letter/j/aeb1de/32.png) [@Jonathan](https://community.fibery.io/u/Jonathan)\ **Post date:** [July 18, 2025, 6:16pm UTC](https://community.fibery.io/t/embed-a-view-in-a-rich-text-field-with-an-automation/9210/2 "2025-07-18T18:16:19Z")
Anyone have an idea? ---
**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:** [July 18, 2025, 6:29pm UTC](https://community.fibery.io/t/embed-a-view-in-a-rich-text-field-with-an-automation/9210/3 "2025-07-18T18:29:25Z")
I’m pretty sure it’s not possible… If you need the view for all the entities you can make a to-many relation view. Do you want to make the view only if it’s a certain condition? What’s the use case? You can’t make the embedded views in automations, but you can copy rich text from another entity using automation (with a embedded view) So there might be a solution here depending on the use case. If it’s for templating. Lmk! ---
**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:** [July 18, 2025, 7:05pm UTC](https://community.fibery.io/t/embed-a-view-in-a-rich-text-field-with-an-automation/9210/4 "2025-07-18T19:05:19Z")
You might want to check out these somewhat-related topics > [@How to create a dynamic link that shows a view filtered by current entity?](https://community.fibery.io/t/how-to-create-a-dynamic-link-that-shows-a-view-filtered-by-current-entity/5152): > > Use case: I want to create a step by step guide in the description field of a meeting entity. The guide is used by the facilitator to fill in meeting information. I do not want to embed fields, but want these to be accessible through a link in the description text. The link needs to open in a new panel at the right, and need to be filtered by the current meeting where the link is clicked. In the screenshot above, I show an example link that wor… > [@Prepopulating views/search/forms using URL parameters](https://community.fibery.io/t/prepopulating-views-search-forms-using-url-parameters/5153): > > This is a feature request to introduce URL parameters to prepopulate stuff in Fibery. For example views, based on variables that can populate the view configuration, or search virables, or form fields. Why is this needed? Because in many cases, creating an embedded view as field relation, or a custom view is too much work and requires massive amounts of custom views to be maintained. The solution is to be able to prepopulate a view using URL parameters… Use cases: Customized User Experiences:…