We have cards created in Trello via a Zoho API. Each card includes several custom fields, including an Event Manager dropdown (first names only).
After the card is reviewed, we use Butler automation to move it to our Booked Events board and generate a checklist with assigned tasks and due dates. Due dates are calculated from the Event Date custom field.
Our current automation works like this:
• A Card Button called “Assign to – [Event Manager Name]” moves the card to the Booked Events board and adds the first batch of checklist items.
• Each checklist item is assigned either to me, our scheduling manager, or the Event Manager, and the due dates are set relative to the Event Date.
Because the checklist is long, the button only creates the first batch of items. The final item in that batch triggers a rule, which adds the next group of checklist items, and so on. In total, it takes one button plus several rules to generate the full checklist.
The problem is that this entire automation sequence has to be duplicated for each Event Manager.
For example:
• “Assign to Allison” → checklist items assigned to me, Scott, or Allison
• “Assign to Naomi” → checklist items assigned to me, Scott, or Naomi
As our team grows, maintaining separate buttons and rule chains for each Event Manager isn’t scalable.
My questions:
Is there a way to use one button and one automation chain that assigns checklist items to the Event Manager based on the value of the Event Manager custom field or some other field or card assignment, instead of hard-coding the name?
I know Butler supports {username}, but that assigns the task to whoever clicked the button. In our case, the sales person clicks the button, not the Event Manager.
Is there a more efficient way to structure this type of automation that I might be missing?
Happy to share screenshots if that would help clarify.
Thanks for any ideas!