In earlier versions of the Airtable node, I could specify tables by their name. However, I now need to use the ID, which presents an issue for several of my workflows that span multiple bases. While older versions of the node remain functional, updating the table 'name' in newer versions removes this capability.
My question is: how can I continue to develop workflows that target tables by name, rather than by ID, when the situation requires it?
Hi, I'm sorry you're encountering this issue. I'm not certain why this limitation was implemented in the current version of the Airtable node. Perhaps someone from our product team can offer more insight.
So, my question is how can I continue to build workflows which target tables by name, instead of ID, when necessary?
For the Airtable API, it shouldn't make a difference as far as I know (they specifically list tableIdOrName
in their API reference). Therefore, I'd suggest using the HTTP Request node instead of callin.io's pre-built Airtable node. While this node might also evolve over time, it seems highly unlikely that its ability to send custom requests will be removed.
To update data in a table specified by name, you could use a workflow similar to this (by calling Airtable’s Update record endpoint):
In the example URL, appwTLCOMpC9wzoUW
is my base ID, Table 1
is my table name, and recMhRV9gH3nuJULS
is the ID of the record I intend to update.
Before:
After:
Hope this helps!
Hi there!
Are you looking to use an expression to specify the table name?
Thanks. Would you prefer to manually enter/select the table name in that field, or configure it using an expression?
Ideally, I'd like the ability to specify a static table name or dynamically use an expression. For my current issue, I could make either option functional.
This discussion was automatically closed 90 days following the last response. New replies are no longer permitted.