Untrue. Scripts can execute based on things that happen in the UI - example - a record moves into a view.
@Nur_Baizura Can you clarify what type of trigger in the front end you want?
Airtable can run scripts in two ways: scripting app and automation scripting actions.
With Scripting app, the script can only be run from a button: either the button in the Scripting app itself, or a button field in a table.
With Automation Scripting actions, the script is run in reaction to a trigger. The trigger can be the result of a data change made in the UI, such as changing the value of a field. An automation can also be triggered when the filter conditions for a view change. The trigger cannot be the result of most UI interaction that do not change data, such as selecting or unselecting a record or viewing a different table.
With a custom app, there are many more possibilities, including changes to the selected record or table. However, custom apps development is a major undertaking, much more complex than script writing.
@Nur_Baizura Can you clarify what type of trigger in the front end you want?
Airtable can run scripts in two ways: scripting app and automation scripting actions.
With Scripting app, the script can only be run from a button: either the button in the Scripting app itself, or a button field in a table.
With Automation Scripting actions, the script is run in reaction to a trigger. The trigger can be the result of a data change made in the UI, such as changing the value of a field. An automation can also be triggered when the filter conditions for a view change. The trigger cannot be the result of most UI interaction that do not change data, such as selecting or unselecting a record or viewing a different table.
With a custom app, there are many more possibilities, including changes to the selected record or table. However, custom apps development is a major undertaking, much more complex than script writing.
Thank you for your further explanation,
The trigger cannot be the result of most UI interaction that do not change data, such as selecting or unselecting a record or viewing a different table.
This explained my requirement would needed more complex development.