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:
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.
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.
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ā.
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
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
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.
I think it would be nice if doing this 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.
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.
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.