Skip to main content
Best answer

Duplicated Trello label detection Zap failing to detect new records


Forum|alt.badge.img

Hello, I’m trying to use a zap that detects a new label added to a card on multiple Trello boards. As far as I can tell this requires a zap for each board. I have this working nicely on one board, but when I duplicate the zap and change the board it will not detect new records for that board. The new board I’m trying to use is a renamed duplicate of the first board, so the labels, etc. are all the same, and Zapier seems to be detecting that the board exists and all the label names on it. When I test, no records appear. I’ve tried many times to add a variety of labels (including default labels) before, during, and after testing with no results. When trying a different trigger it does detect new records. I haven’t tested this exhaustively but it seems specific to the “new label added” trigger. The weird part is when I create a new zap from scratch and use the same setting, board, etc., it does detect new records. Furthermore, when duplicating the zap and leaving the board the same

The only difference I see is the fact that it’s a duplicate Zap. I’ve tried creating a new board rather than duplicating, and also tried using older existing boards. When ignoring the test and publishing the Zap it doesn’t run when the label is added.

Any help is appreciated, thanks.

 

Best answer by JasonbergBest answer by Jasonberg

I contacted support and it turns out this is a known issue. Duplicating a Zap that uses the instant trigger “New Label added to card” and then changing the board will result in the new Zap failing to detect activity on the new board.

View original
Did this topic help you find an answer to your question?

7 replies

Troy Tessalone
Forum|alt.badge.img+14

Hi @Jasonberg 

Good question.

If you suspect an issue with the duplicating of a Zap, then you can try opening a ticket with Zapier Support: https://zapier.com/app/get-help


Forum|alt.badge.img
  • Author
  • Beginner
  • 3 replies
  • Answer
  • December 13, 2023

I contacted support and it turns out this is a known issue. Duplicating a Zap that uses the instant trigger “New Label added to card” and then changing the board will result in the new Zap failing to detect activity on the new board.


ken.a
Forum|alt.badge.img+6
  • Zapier Staff
  • 6324 replies
  • December 13, 2023

Thanks for looping back for an update here @Jasonberg, and I’m sorry to hear about the issue being a bug.

If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help.


Forum|alt.badge.img
  • Author
  • Beginner
  • 3 replies
  • September 1, 2024

Update: This bug is still present but using Webhooks gets around the issue completely. Webhooks in general seem preferable if you’re trying to use zaps across multiple Trello boards, because you can simply have rules and buttons that post to a common url, rather than setting up a Zap for each board.


  • New
  • 1 reply
  • January 30, 2025

@Jasonberg can you elaborate on how to use webhooks to solve this problem? I’m trying to use zaps on multiple boards to create a row in a spreadsheet and am having the same issues with the client label not showing up. 


Forum|alt.badge.img
  • Author
  • Beginner
  • 3 replies
  • January 30, 2025

@ldubs1116 Sure-  you have to set up a rule (or button) in Trello that posts to the webhook url provided by Zapier. To get that url you just create a webhook step and go to the test tab.

On the Trello side, when selecting what actions your automation performs, go to the bottom of the content tab and find ‘get’. Change this to ‘post to’ and paste your url. The payload is the data you send to Zapier and must be formatted as json. All the Trello markdown stuff works here, {cardname}, etc.

Trigger your rule and if done right you’ll receive test data on your webhook. Any time this wasn’t working for me it was because I hadn’t properly formatted the json.

As an example, here’s json that sends the card id, card name, and cards board name. The card id can be useful if you need to perform an action on the card after the zap is triggered.

 

{
    "cardid": "{cardid}",
    "cardname": "{cardname}",
    "cardboardname": "{cardboardname}"
}


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7304 replies
  • February 4, 2025

Hey folks! 👋

@Jasonberg, thank you so much for following up to share details of the workaround you implemented—love seeing folks helping each other out like this! 🤗🧡

I checked on the bug report that Support added you to, and it looks like it was marked as resolved before ldubs1116 reached out here. 

@ldubs1116, if you’re still experiencing issues with the New Label Added to Card trigger, please reach out to our Support team so they can investigate further. Since the previous bug report was closed, this might be a new bug that needs to be addressed. Hopefully Jasonberg’s workaround will help to keep your Zaps running in the meantime! 🤞