Thanks, but the name is a little too tricky. There could be multiple rows with the same title at the moment, plus it’s a user editable field. Does the “name” have to be the tagged column? If not, I could just create a column with a guaranteed unique field.
To be clear, I’m looking to set up a button that links to a webhook and passes information to a third-party tool, which manipulates it and passes it back (effectively a Zapier “Zap” like interaction, but without Zapier as we don’t want to migrate to that system); I want the passed back value to go to the row on which the button was triggered. Whilst the interaction should be fairly instantaneous, we have a number of people working on this doc simultaneously, so it’s certainly possible that the tagged column get change without someone realising.
EDIT: Actually, thinking about this more closely, it’s a guarantee that we will have identical names within the data set. I’m using the table as a cross-channel content scheduler, storing everything from long-form articles to social media posts, but we have functionality where you can “push” an article to social media and use the fact that the “name” is the same to track that relationship. I’ll be able to use “name” for genuinely instant interactions, but any kind of long-form tracking requires access to the ID, so it’s a shame I can’t access it from within Coda directly.