The left-hand panel of the editor allows us to create input variables from triggers and actions that occur before the “run script” action. You’ll be presented with a script editor window, albeit one that is slightly different from the regular script editor. Click on the “Add action” button and select “Run script” from the options: (If you’re following this on your base, make sure that at least one of the record is marked as completed or the test will fail.) Test the condition to make sure it is set up correctly. Pick your table from the dropdown and add the condition - in this case when the “Completed” field is checked. Your “do something” is probably a lot more complicated and useful.Īnd selecting “When a record matches conditions” as out trigger. This isn’t a real world scenario - you are unlikely to want to do this - but we’re going for a simple “do something” here. In my case, the “do something” is write “Task completed” into the script output field. When I complete the task by clicking on the checkbox, I want the automation to run against the selected record, trigger my script and do something. My base is very simple - I have a task name field, a “completed” checkbox field and a “script output” text field: Let’s do some set up to show how this works. Like many Airtable users I’ve used Zapier, Integromat and other methods to automate actions on my bases, but the Airtable Automations feature brings this in-house, reducing the number of tools and apps I need to get a job done.Īs a script enthusiast, I think it’s fantastic that Airtable have built scripts into the Automations toolkit from the start, but the interaction of triggers and scripts isn’t completely obvious, so this post will show how to incorporate scripts into Automations. Then create an automation with a logical trigger to set the value of the number.Alongside the introduction of scripts, one of the big leaps forward in Airtable functionality in 2020 was the Automations feature. Change the field permissions so that users cannot directly edit the field, but automations can set the value. Change the table permissions so that no-one can add/delete records in the table. Store the number in a table in the same base. However, it is possible to provide protection against accidental changes without storing the number in a different base, using table and field editing permissions. People are less likely to accidentally update the number. This method does not require revealing your api key.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |