About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Find / Create Trello Card creates duplicate

  • 19 June 2020
  • 3 replies
  • 162 views
U
Userlevel 1

Hi, I have set up a new Zap integrating ScheduleOnce Booking with Finding/Creating a new card in Trello.

The behavior I want is:

  1. the first time someone books in a Sales call via ScheduleOnce they get added to the Pipeline Board.
  2. However when they are later converted into a client and then book in a subseqent 1:1 session (again via ScheduleOnce but in a different Booking Form) I don’t want a new card created (currently in Zapier you can’t differentiate between different ScheduleOnce Booking Forms)
  3. Ideally it would update the existing card with new information from the latest session booked in, but I”ll settle for no duplicated cards!

I can’t get it to do this.

Instead it creates a new card initially, but when a subsequent booking comes in for the same client (I’m using their email address as the Organisation ID) it just creates a new card.

What do i need to do / change in order for it to FIND an existing Card and:

  1. Not create a duplicate
  2. update the original

Thanks.

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

steph.n
Userlevel 7
Badge +8

Hi there @UK_Natalie - Thanks for writing to us today! It sounds like you need to separate this into two Zaps: 1.) when a client is new and books a session, then  2.) a new zap for the different booking form that has a step that is Create a Trello “Find Card” step then Update existing card with the found card.

Could you give this a try and see if that helps? Thanks!

U
Userlevel 1

HI STeph, thanks for that. 

The challenge is there is no way within the Zapier > ScheduleOnce integration to identify different Booking Forms.  This means all “ScheduleOnce” triggers are applied no matter which booking form is used.  Therefore I can’t identify between a NEW client vs an EXISTING client so the solution you recommended wouldn’t work.

 

My attempted solution to this was to use the Trello “Find A Card” action. 

I had hoped that I could set it so that:

  1. if it FOUND a card (ie. it was an existing client) it would either update it, or at the very least NOT create a new one. And
  2. if it DIDN’T find a card (ie. it’s a new client) it would create a new card.

However if appears the “Find A Card” action can’t actually find an existing card.

Can you please explain what fields Zapier uses to match an exising card in Trello?

Is it the Card Name?

Thank you.

 

steph.n
Userlevel 7
Badge +8

Hi @UK_Natalie - Could you confirm with me to see if you’re using “Find a Card” or “Find or Create Card” action? I think the appropriate one would be “Find or Create Card.” You can learn more about the integration here on our Zapbook for Trello: https://zapier.com/apps/trello/integrations - If you scroll down and click on “Searches (12)” tab, you’ll notice the difference in Actions:

 

 

Terms & Conditions