šŸ‘‚ Feedback needed: scripts in automations that shouldn't be scripts

+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:

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.

5 Likes

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ā€.

Concatenate an encoded URL

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.

1 Like

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:

If I choose script I get this:

This section doesnā€™t allow for AI but it would help tremendously and make customersā€™ experience better and less complex.

Can you clarify this please? Do you want to use AI from this section or create script using AI?

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.

This is in progress already

3 Likes

2 posts were merged into an existing topic: Webhook Action in Automations

@Robert_B Related! šŸ¤– Feature Request: AI Generation for Scripts

Very glad to hear this is in progress. Any timeline? I know back in Feb this was not any where near on the roadmap.

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.

2 Likes

This would be great! We regularly turn meetings into other things, like a reference article or into a new project.

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.

4 Likes

Awesome if automations can be improved :heart_eyes::heart_eyes::heart_eyes:

High prio for us

Awesome, but lower prio
Since we already found a solution. But would be great if we can simplify our (quite complex) workspace.

Recurring tasks

4 Likes

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.

7 Likes

Ability use UUID in a formula or automation

8 Likes

Also the ability to reference Public Id in formulas.

And return null/empty from Formulas that return a Collection.

1 Like

This is already possibleā€¦unless Iā€™m misunderstanding the request.

Can you give an example of how you might use this