Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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.

We have two zaps created to move Mojo contacts to Kvcore.

 

zap 1 is when a new contact is added to a Mojo group it is then pushed to KVcore.

 

zap 2 is when a contact is updated in Mojo that it should be pushed to update in KVcore.

 

Instead zap 2 is making a full new contact. So we now have two contacts in Kvcore.

 

any help?

Hi @Santa Clarita Homes 

Good question.

We will need to see detailed screenshots with how your Zap steps are configured to have context, thanks.

Hi @Santa Clarita Homes 

I’m sorry you’re running into this known bug with the Update Contact action in KVCore.

I’ve added you to the list of affected users. I don’t know when this bug will be addressed, but the good news is that the KVCore developers who built this integration have access to all the bug-related info there. 

With your email address listed there, you’ll be the first to get any updates when this bug is fixed.

Let me know if you have any questions

Reply


Terms & Conditions