# Template Processing Functions in Scripts

**URL:** https://community.fibery.io/t/template-processing-functions-in-scripts/2832
**Category:** Ideas & Features
**Tags:** automations, rich-text
**Created:** [May 21, 2022, 6:20pm UTC](https://community.fibery.io/t/template-processing-functions-in-scripts/2832 "2022-05-21T18:20:21Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)
#### Post date: [May 21, 2022, 6:20pm UTC](https://community.fibery.io/t/template-processing-functions-in-scripts/2832/1 "2022-05-21T18:20:21Z")

</div>

Fibery’s support for [markdown templates](https://help.fibery.io/en/articles/5170015-markdown-templates) is pretty great and I use them often for automations when creating new entities. However, I am finding that some of more generic entity types, like meetings, require that I use different types templates depending on the situation. This is dealt with by introducing a higher level “type” entity like “Project Type” or “Meeting Type” (process is also [described here](https://help.fibery.io/en/articles/6224116-how-to-create-a-template-repetitive-process)) .

However, one thing that is missing with this process is that you no longer have access to the markdown template features, such as embedding variables or lists (or [recently added functions](https://community.fibery.io/t/changelog-may-12-2022-no-data-loss-in-docs-more-options-in-automation-templates-search-in-my-space-17-fixed-bugs/2790)). So I was wondering if it is possible to expose the template processing/parsing functions in the automations for templates that are not explicitly defined inside an automation. This might be two separate requests:

1. Have access in automation scripts a function (or series of functions) to parse templates from fields (assume that is something that already exists in the backend), and

2. Have the ability to pass a text field or a rich text field instead of writing out the template content:

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

This not only would open up possibilities for templates for rich text fields, but hopefully allows templates for other fields (like the name field).

I hope that makes sense 🙂