Create a “group” condition for automation recipes. While we can work around it by having an automation “when group changes, set status to something” then use the status as the conditional, this is a bad solution for the following reasons:
Creates a potential race condition - anything triggered by the group change, triggers before that status change happens. Any further automations triggered cannot rely on that status to decide to run or not.
Increases load on the platform - every single instance of this “boilerplate” automations is another trigger that has to be processed, and action be taken.
Adding “group” as a condition in automation recipes will streamline board creation, reduces platform load (and hence automation latency), and reduce the chance of creating race conditions where two automations are dependent on each completing executing at the same time.
I have a use case example for this, please don’t beat me up too bad if there is another way to accomplish this process.
We use a Status column for what I will call the “Stage” an item is in. For example: Agenda, Queued, In-Process, Completed. When we create a new item we need a recipe that says:
When an Item is created AND Group is Agenda set Stage to Agenda.
I’m sure there are much more complex scenarios, mine is simple.
Thats a good one. While the standard workaround for this is to have a column that is the group, and an automation of “when item moves to agenda… set status to agenda” this won’t do anything for a NEW item because it didnt move to the group - it was created in the group.
I’ve gotten around this in the past when needed in the workflow using Integromat. I make a status column in the board called “groupmirror” using the API directly. This way the column ID is “groupmirror”. I then configure it with status labels that exactly match the group titles (which again I create with the API so they are usable and meaningful at the lower level not just display level). Then I set up a webhook on the board for when an item is created, and integromat just maps the boardid, itemid, and then the group id to the status label. IT works.
The reason I shared the above is simple - thats the level of workaround its required for me to achieve having something set like that on creation. This way any automations that depend on group, i can use this groupmirror status as the criteria. Then one of my recipe actions is “set group mirror to ____” right before “move item to group”.
In your case you could use integromat to set the stage status to agenda as needed. That said if ALL new items must be created in agenda, you could set the item defaults on the board for stage to be Agenda.