I can see the details about tags mutation on the developers site.
Do you know if a “public board” is a Main board or a Shareable board, or both? (It’s a little disconcerting that some documentation is inconsistent in the terminology or not explicit enough.)
I can still see that there is a benefit in using tags, but only where the tags persist across multiple boards.
But I also understand that implementing a condition like this within a recipe may not be possible, and would definitely have a negative impact on both UI and UX.
I did some more investigation into tags since my previous message. All I found was that the overall implementation of tag management appears to be problematic. Tags data does not appear to include the type of board that it is associated with, just the board id; so that’s another lookup that would be required before determining how that could be presented to a user.
Also for a tag that is used on multiple boards, I can’t see what happens when one of those boards is subsequently made private. I’m guessing that the tag then has two instances that are disconnected.
And there doesn’t appear to be any way of deleting tags across an account, although you can readily list them in a query.
While I had thought this might be a good use case for tags, it appears that the overall implementation and management of tags is problematic.
If the tag management included user control of the scope of the tag, then it might work well.
Maybe this idea needs to be shelved until that functionality is available?