Welcome to the community, @Jose_Mendez! :grinning_face_with_big_eyes: The limit you’re seeing isn’t based on a specific number of fields. Chances are you have some fields that Airtable doesn’t currently provide access to via the automations system. Could you describe your setup in greater detail, including the field types of the fields you want to use in the automation?
Hi Jose, am also new to Airtable and am trying to get my bases to update when a new record is entered in a Google sheet. However, the automation requires each of the fields to be specified - and I have a very large number. So, how exactly did you get your automation to work.
Also though the notification says test ran successfully, I can’t see any corresponding updated values.
Also, though the automation runs and gives results on testing, when I select Google sheets in the trigger part, I get a notification saying that the spreadsheets aren’t supported.
Also, how does one run an automation manually? Does it happen when you switch it on? Tried that and nothing seems to happen. The only way to get it to happen seems to be by testing again.
Welcome to the community, @Atul_Londhe! :grinning_face_with_big_eyes:
An automation runs based on a trigger. Turning an automation on just tells Airable to begin watching for that trigger. Automations can only be run when that trigger activates. In the case of Google Sheets, the trigger is the creation of a new row in a spreadsheet. Once that happens, all data in that row is available in later steps in the automation.
The timing of the trigger is important to know. As the name implies, the Google Sheets trigger fires when a row is created, and the data sent to Airtable is the data in that row at the moment of its creation. If the row is created, and then data is added to various cells in that row after its creation, those cells’ contents won’t get passed to Airtable. The same thing goes for new records created in Airtable. If an automation trigger is “When record created”, the only data sent to the automation is data available at the time of the record’s creation.
Can you be more specific re: the error message? You can take a screenshot and drop that into a reply, which will provided the clearest picture (literally) of the problem.
Thanks for a very clear and informative reply and for taking time out on New Year’s Eve to do it.
The reason I asked about triggering the automation manually (contradiction in terms!) is that I’m on the free plan and I had misread the plan details which actually said that syncing tables was manual on the free plan but I had initially thought that that it was talking about automations. So, that was confusion on my part.
As regards the ‘error message’ I’m pasting a screenshot below to provide a ‘clear picture’ : ) as you had suggested:
The message is in the red rectangle.
Just to provide a bit of context, what I’m trying to do is import a row from a Google sheet which has over a hundred columns into Airtable. I was trying to figure out a way of automating the importation of the whole row at one shot i.e. without having to specify each field in Airtable and what needs to go in each field. What I’m really interested in is finding out if there is some way of doing this.
When I tried to do this using a Zap instead, there were problems which I am currently looking into and which may be related to the error I’m getting in Airtable.
It would be great if you could let me know how to update a whole row without having to specify the details since with over a hundred fields, it becomes very tedious and leaves lots of room for error.
Thanks again for your prompt and helpful reply.
Thanks for posting the screenshot. The key phrase in that error message is “shared drives.” In short, Airtable can only access spreadsheets that you created in your own Google account. If the spreadsheet was shared by someone else, it’s not available.
Unfortunately Airtable doesn’t provide a way to add data by position (i.e. column 1 from the spreadsheet goes into the first field in Airtable, column 2 into the second field, etc.). This is probably because field order in Airtable isn’t static. Each view can have the fields (with the exception of the primary field) in different positions. Whether you’re using the import features or an automation, you need to manually specify which field will receive each column’s data.
That explains it. This is very clear and informative and really helps. Thanks a ton for your support.
A couple of other questions:
Since there are over a hundred columns in the Google sheet information from which has to be imported into Airtable fields, in principle, will automation be able to handle it (once the shared sheet problem has been overcome that is?)
Will changing the names of the fields in Airtable mess up the automation?
In Zapier, there is an automation that creates a new row in Airtable when a Google sheet record is either updated or created. Does this mean that updated Google sheet records will result in new rows in Airtable bases?