# 👂 Feedback needed: scripts in automations that shouldn't be scripts **URL:** \ **Category:** News & Announcements\ **Created:** [August 28, 2024, 8:05am UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560 "2024-08-28T08:05:12Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![Dimitri\_S](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dimitri_s/32/1683_2.png) [@Dimitri\_S](https://community.fibery.io/u/Dimitri_S)\ **Post date:** [August 28, 2024, 10:29pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/21 "2024-08-28T22:29:50Z")
+1 for formulas getting some love. I’ve largely moved away from using scripts for automations because they are so fragile because unlike automations the code doesn’t get updated when you change field names and the code is hidden away and easy to forget unlike formula fields. That being said, a few use case where formula fields aren’t sufficient and I’ve almost had to result to scripts is for required field validation. I know it’s hard to implement in Fibery but even a soft validation of “if this field is empty make this other field border red” or similar would be nice. Not that you can do it in scripts… I have been tempted to use scripts to send a Slack message or similar notification after some time. Otherwise up end up with a rather ugly formula like this: ![1000007378](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/6daf58573faf34c66b59be4505b6777408f9ebb6.jpeg) ---
**Author:** ![Dimitri\_S](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dimitri_s/32/1683_2.png) [@Dimitri\_S](https://community.fibery.io/u/Dimitri_S)\ **Post date:** [August 28, 2024, 10:39pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/22 "2024-08-28T22:39:15Z")
Can’t you do intervals of 12 months already? I believe for one test automation where I wanted it to only ever run once I was able to set it to 88 months. ---
**Author:** ![JackC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jackc/32/5420_2.png) [@JackC](https://community.fibery.io/u/JackC)\ **Post date:** [August 29, 2024, 2:21am UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/23 "2024-08-29T02:21:57Z")
The most encountered one for me is that adding a thing to a multiple select field (without removing the existing things) requires a script. Can’t even do it as a formula as far as I can tell. It shouldn’t be that complicated. The other one that would be useful is formulas in the automation filters. So many formula fields that just equate to “does this one automation that runs monthly pick this?” and don’t need to be recalculated every time anything relevant changes. ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [August 29, 2024, 6:36am UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/24 "2024-08-29T06:36:12Z")
It seems like you’re talking about the frequency of the automation to run (like if it is running on schedule). I’m talking about a filter for an entity’s field, for example “modification date”. For “is within” there is the option of “the next year”, but for all the other date filters (like “is before” and “is after”) the furthest you can go is “one month ago” or “one month from now”. ---
**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:** [August 29, 2024, 2:09pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/25 "2024-08-29T14:09:13Z")
**Concatenate an encoded URL** > [@New Formula: URL Encoder](https://community.fibery.io/t/new-formula-url-encoder/6310): > > It would be great to have encode and decode formulas generating URLs. I currently use scripts to generate pre-filled Calendly URLs. All the values are in Fibery already but scripts are the only way to encode text. **Automatically set State or Select Fields** I have to use a script to read text fields (from integrations) or extract data from date fields to set the value of State fields and select fields. Examples: - convert the Deal Stage from Hubspot Integration to a Fibery State. - set the “Quarter” dropdown given the fiscal quarter of the date field in the Payments database It would be great if we could set rules for these field types just as we do for relation fields. **Call a webhook/URL** > [@Emit Webhook as an Action](https://community.fibery.io/t/emit-webhook-as-an-action/5002): > > I’m looking to loop external softwares into actions taken within Fibery. For example, whenever an automation is triggered or a button pressed, I’d want to be able to emit a network call to a specific endpoint, and include query param and body data, pulled dynamically from the entity that triggered the automation (or table which owns the button). Is this possible, currently? It would let me use other services like Make or N8N for very complex automation workflows, based on events from within Fibe… It’d be a significant UX improvement to create a webhook action instead of writing JS to call webhooks. **Using the Outputs of Prior Script Steps** > [@Do automation actions return step results? Can we use them further down the automation stack?](https://community.fibery.io/t/do-automation-actions-return-step-results-can-we-use-them-further-down-the-automation-stack/4373/2): > > In my experience, no. I hope this is an update released this year. This kind of functionality makes developing in Airtable quick and easy. It would no doubt save time when building in Fibery too. In my case I need to generate an 8 character alphanumeric string as part of a user friendly ID. This part is easily handled by a script. It would be ideal if I can simply return this string from the script and then reference it as a step result later in my automation. Many low-code builders allow for thew use of scripts within the workflow and setting properties with the UI. Zapier, HubSpot, and Airtable come to mind most easily. Right now, only other script actions can use the outputs from a script action. In practice, we want to update properties, add the outputs to emails or slack messages using the outputs of a script. ---
**Author:** ![Robert\_B](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/robert_b/32/7198_2.png) [@Robert\_B](https://community.fibery.io/u/Robert_B)\ **Post date:** [August 29, 2024, 7:12pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/26 "2024-08-29T19:12:30Z")
Hi Antonio, I want to share something that I think would be a fantastic addition - though it’s kind of the opposite of what you’re asking! There is a script area that could hugely benefit from AI: If I want to add a button: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/bcd7bb085e8ece3edc4ad7aaf579918239b7eae4.png) If I choose script I get this: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/1a93c933926dc4ca94704f64c4a60ea9f3016987.png) This section doesn’t allow for AI but it would help tremendously and make customers’ experience better and less complex. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 30, 2024, 5:44am UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/27 "2024-08-30T05:44:06Z")
> [@Robert\_B](#): > > This section doesn’t allow for AI Can you clarify this please? Do you want to use AI from this section or create script using AI? ---
**Author:** ![Robert\_B](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/robert_b/32/7198_2.png) [@Robert\_B](https://community.fibery.io/u/Robert_B)\ **Post date:** [August 30, 2024, 1:27pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/28 "2024-08-30T13:27:48Z")
Yes, create/edit script with AI like n8n, pipedream, zaiper do it in similar contexts - getting the aid of ai would be very helpful here. I more aggressively tried out the ai space building/modifications of Fibery more recently and it’s extremely good. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 30, 2024, 1:29pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/29 "2024-08-30T13:29:02Z")
> [@Robert\_B](#): > > Yes, create/edit script with AI like n8n, pipedream, zaiper do it in similar contexts - getting the aid of ai would be very helpful here. This is in progress already ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 2, 2024, 6:41am UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/30 "2024-10-02T06:41:36Z")
2 posts were merged into an existing topic: [Webhook Action in Automations](https://community.fibery.io/t/webhook-action-in-automations/7485/4) ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [August 31, 2024, 9:10pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/31 "2024-08-31T21:10:26Z")
> [@Robert\_B](#): > > Yes, create/edit script with AI like n8n, pipedream, zaiper do it in similar contexts - getting the aid of ai would be very helpful here. @Robert_B Related! [🤖 Feature Request: AI Generation for Scripts](https://community.fibery.io/t/feature-request-ai-generation-for-scripts/5337) > [@mdubakov](#): > > This is in progress already Very glad to hear this is in progress. Any timeline? I know back in Feb this was not any where near on the roadmap. ---
**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:** [September 3, 2024, 11:41am UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/33 "2024-09-03T11:41:20Z")
I think it would be nice if [doing this](https://community.fibery.io/t/cloning-an-entity-and-re-mapping-where-it-is-mentioned/6578) didn’t require a script, but it’s probably not something that needs to be available in automations, just added (as an option?) to the existing ‘Convert to …’ functionality. ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [September 3, 2024, 12:13pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/34 "2024-09-03T12:13:01Z")
This would be great! We regularly turn meetings into other things, like a reference article or into a new project. ---
**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:** [September 9, 2024, 9:50pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/35 "2024-09-09T21:50:54Z")
I noticed today that making changes to the rich text field in my wiki database did not update the modification date for the entity. I created a rule that checks a box, uses a script to wait a few seconds, then unchecks the box but it’d be nice to have a setting that lets us include rich text field changes in the calculation. ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [September 11, 2024, 5:08pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/36 "2024-09-11T17:08:19Z")
Awesome if automations can be improved 😍😍😍 **High prio for us** > [@interr0bangr](#): > > Formulas within automation filters! Would unlock so much more power and minimize many complex workarounds for things. > [@interr0bangr](#): > > - There’s no way to do multiple/splitting paths (IF statements) in automations without a script. > [@interr0bangr](#): > > There’s no way to do auto-links with any other condition besides EQUALS, which means we often need to rely on scripts to link related entities for CONTAINS/IS ONE OF scenarios. > [@interr0bangr](#): > > “Union” function (essentially the existing “Join” function, only with references to entities instead of just a text field) > [@interr0bangr](#): > > “ToNumber” function\*\* (the opposite of the existing “ToText” function) > [@interr0bangr](#): > > When using the “Link entity” action in automations, you can use a formula, but when you use the “Unlink entity” action, you cannot use formulas. > [@interr0bangr](#): > > There is a “User Input” option for button automations, but not for rule automations. > [@helloitse](#): > > Automatically set State or Select Fields > [@Automations: Support entity references like "\[Step 1 linked item\]" in markdown-template Actions](https://community.fibery.io/t/automations-support-entity-references-like-step-1-linked-item-in-markdown-template-actions/5715): > > Unlike formulas, automation markdown-template Actions (e.g. “Append to Document”) do not currently support Rule-entity references like [Step 1 linked item]. > [@Matt\_Blais](#): > > Transcluding fields from other entities (i.e., JOINs) **Awesome, but lower prio** Since we already found a solution. But would be great if we can simplify our (quite complex) workspace. > [@sereganabokar](#): > > Sending notifications in Telegram. Recurring tasks > [@njyo](#): > > Would be nice if the whole thing can just be compiled with Markdown. Also, the formatting of dates and date ranges is still very unclear. > [@njyo](#): > > Setting icon, states and emojis if formula: > [@helloitse](#): > > Call a webhook/URL ---
**Author:** ![Oleg](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oleg/32/1887_2.png) [@Oleg](https://community.fibery.io/u/Oleg)\ **Post date:** [September 20, 2024, 11:21am UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/37 "2024-09-20T11:21:38Z")
Hello, > Very glad to hear this is in progress. Any timeline? I know back in Feb this was not any where near on the roadmap. AI Script Assistant (BETA) is already available as a part of existing AI Assistant. Feel free to try by asking the desired script for your database. We are still working on improvements, but error rate of scripts generation is pretty low. Please give a try and let us know about your thoughts. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9027dfc18d44ecdb1b56d2c57f63cf6768a55d18.jpeg) ---
**Author:** ![Lee\_Denny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lee_denny/32/8158_2.png) [@Lee\_Denny](https://community.fibery.io/u/Lee_Denny)\ **Post date:** [September 23, 2024, 2:06pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/38 "2024-09-23T14:06:52Z")
Ability use UUID in a formula or automation ---
**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:** [September 23, 2024, 8:40pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/39 "2024-09-23T20:40:56Z")
Also the ability to reference `Public Id` in formulas. And return null/empty from Formulas that return a Collection. ---
**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:** [September 23, 2024, 9:20pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/40 "2024-09-23T21:20:15Z")
> [@Matt\_Blais](#): > > the ability to reference `Public Id` in formulas. This is already possible…unless I’m misunderstanding the request. ---
**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:** [September 23, 2024, 9:20pm UTC](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/41 "2024-09-23T21:20:54Z")
> [@Matt\_Blais](#): > > return null/empty from Formulas that return a Collection Can you give an example of how you might use this [Previous page](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560.md?page=1) [Next page](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560.md?page=3)