If you’re looking for a less “codey” approach, you can try Zapier, which is designed to automate tasks that involve multiple services (Airtable and Gmail, for example), and has a library of pre-made automation workflows to boot.
Otherwise you might want to provide an example of what your data and workflow look like because I’m not too sure what you want to automate.
If you’re looking for a less “codey” approach, you can try Zapier, which is designed to automate tasks that involve multiple services (Airtable and Gmail, for example), and has a library of pre-made automation workflows to boot.
Otherwise you might want to provide an example of what your data and workflow look like because I’m not too sure what you want to automate.
Apologies it was a very waffled summary
I tend to want to structure kanban views by fields that are lookup values from another table. But as I understand it you can only structure them by single select fields?
Now I mimic that referenced value is a single lookup, works but a bit clunky.
Regards
Rob
Apologies it was a very waffled summary
I tend to want to structure kanban views by fields that are lookup values from another table. But as I understand it you can only structure them by single select fields?
Now I mimic that referenced value is a single lookup, works but a bit clunky.
Regards
Rob
Ah, thanks for clarifying! (Sorry I lost track of this thread.)
Bad news: You’ve already got the best current solution (you can automate the field copying with Zapier, but that’s about as much as you can do).
Good news(?): They might add lookup fields as a base field in Kanban view the way they did with Calendar view.
There’s an existing thread, but it’s not under the Feature Requests sub-forum. You may wish to create a new topic there, or invite one of the dev team to look at the original thread.