Help

Airtable Cobuilder is here! Learn more about our new no-code app creation feature, powered by AI on the Airtable Academy

Re: Is it possible to execute a script from a mobile device

4871 0
cancel
Showing results for 
Search instead for 
Did you mean: 
Lee_Mandell
6 - Interface Innovator
6 - Interface Innovator

I have a script I want to run to speed up data entry but I can’t figure out how to run it from a mobile device. The button support is too limited on the mobile app. Has anyone been able to run scripts on a mobile device?

13 Replies 13

Yes.

Create an automation (using the desktop UI) that detects record change events and runs scripts as a result of these changes.

Lee_Mandell
6 - Interface Innovator
6 - Interface Innovator

Unfortunately, the scripts associated with automations are even more limited than the regular scripts. I need to be able to query the user and that is not available. I’m basically trying to create a streamlined data entry system. I’m entering data in both the main record and creating linked records but most of the time only need a couple of pieces of data from the user and the rest can be determined programatically. I was hoping to do this in airtable but it will probably have to be done using airtable’s main api.

Setting aside the processing constraints (CPU and execution time) name something that cannot be handled by a script action?

How about …

  1. Create a new table with the inputs that the user needs to enter.
  2. Create a form for the table.
  3. Create a scripting automation action for when there is a new record (or when record matches conditions).
  4. Have the mobile users enter data using the Airtable form.

The biggest things that I see missing are that from a script associated with an automation you can’t get user input with calls such as input.textAsync that you can with a scripting app. In addition I can’t figure out a way to fire off a scripting app from a mobile device. Maybe I’m just missing something obvious.

That’s an interesting approach and will give it a try. I have found forms to be pretty clunky and I might just be able to use a view to achieve the same thing. From a database design perspective the thought of having to create a table just to do data entry into another table does not sound good. I would also need to delete the record right away to make sure I don’t have any more denormalized data laying around than absolutely necessary.

Wait. What!?!

The entire point of automated processes is to remove human dependencies. By definition, an automation process that depends on human interaction is not automated.

Airtable actions were created with express objective that they work without interruption. What you are describing is a workflow, not an automation process.

Yes, I agree. I’m trying to develop an efficient workflow. I’m using airtable to help manage a farm. Right now using basic airtable functionality it requires scanning a QR code, 7-8 taps and entering data into 4 fields to record a harvest event. This process is repeated 50-100 times twice a week so speeding it up can increase productivity quite a bit. For a vast majority of the time all that is needed is the scan of the QR code and entering data into one field. The rest can be determined programatically. Default values for date fields and single select fields would help a great deal. I tried doing that part with automations but the lag time is so long that it defeats the purpose of trying to reduce the time for data entry. If I could have a button that could call a scripting app on a mobile device I could probably do what I want to but that isn’t supported at this time. The only reason I was trying to coerce automations was that it was the only tool I could think of other than to roll my own from a React app that is running other parts of the farm. I hope this makes some sense.

Expanding on my previous suggestion, you could have a button field that prefills the form used for data entry. While button fields cannot run scripts on mobile, they can open urls.

You can also have the scripting action delete the triggering record, if you don’t want it around cluttering the base.