Hello,
I'm a Trello beginner and just found out about automation.
My current board had many cards that were filled with countless checklists, so I wanted to find a solution to make it more organized.
I thought of an automation that would allow me to create a list of cards that would all be linked to a newly created card :
when a card is created in list "X" on board "Y, find a card titled "1" in list "TEmplate" on board "Z", copy the card to the top of list "{triggercardname}" on board "Z", find a card titled "{triggercardname}" on board "Y", link the cards together
(repeated 7 times for 7 different card templates)
However, I would like to update the list name on board "Z" automatically whenever "triggercardname" is modified. Is it possible ? I couldn't find a "when card name is modified" in the triggers.
Thanks a lot in advance !
Hi!
You're right — there's no direct "when card name is changed" trigger in Butler. It existed in the old Butler Bot days, but was removed when Butler was integrated into Trello
natively.
Partial workaround:
There is a trigger under Card Content: "when the name of a card starts with/contains {*}" (where {*} matches any text). In theory, you could use it to detect name changes and
then use the rename list action (which does exist in Butler) to update the list name on board "Z".
However, there's a significant limitation: https://community.atlassian.com/forums/Trello-questions/Butler-Trigger-quot-When-the-name-or-the-description-of-a-card/qaq-p/1982310
If other team members rename the card — it won't trigger.
If you're the only one renaming cards, try this rule:
When the name of a card in list "X" on board "Y" contains "{*}", rename list "{triggercardname}" on board "Z"
(You'd need to figure out how to target the correct list — this may require the find/lookup actions.)
If multiple people rename cards, Butler alone won't reliably solve this. You'd need Zapier with the Trello trigger "Card Renamed" → action "Update List" via Trello API.
Alternative approach: Instead of renaming lists, consider using a card description or custom field to store the client name, and keep the list names static. This avoids the
sync problem entirely.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.