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.

Keap Max Classic - Keap integration (from jotform) having 2 new issues.

  1. keap contact billing address fields being wiped-out - this is on Zaps when I don’t even have any billing address fields included in the Zap so why would any updates be done to those billing address fields (street, city, country, etc.)
  2. for a different Zap where I update the country code, I have a translator built-in to pass the alpha-3 country code & that’s recently stopped working to update the Keap billing country code properly (updates with the code as invalid)

Hi and welcome to the Community ​@Keap NH! 🎉

1. keap contact billing address fields being wiped-out - this is on Zaps when I don’t even have any billing address fields included in the Zap so why would any updates be done to those billing address fields (street, city, country, etc.)

I did some checking and found a bug report that matches this behaviour. So I’ve added you to the list of folks being impacted by this. We can’t provide a timeline for a fix, but you’ll definitely be notified via email as soon as it’s been sorted out by Keap’s developers.

2. for a different Zap where I update the country code, I have a translator built-in to pass the alpha-3 country code & that’s recently stopped working to update the Keap billing country code properly (updates with the code as invalid)

For this issue, it sounds like the issue is caused by the ‘translator’ action side of things, rather than on the Keap action—is that correct?

Can you share some screenshots showing the current set up of the action is being using to convert the country codes, as well as any errors you’re seeing in the Zap? Make sure to blur or remove all personal information (names, emails, addresses etc.) from screenshots before sharing - you can use a tool like Zappy for that.

Looking forward to hearing from you!

Thanks for your feedback!

  1. as for my first issue with billing address data being wiped-out when zaps are updating contact records.  Thank you for confirming this is a known bug and posting my account to that list to be notified when there’s a resolution.  Is there #/area I can reference and monitor this bug progress?  Might we know when this will be fixed?
     
  2. as for my second issue regarding Country Code integration to Keap contact records - the translator (google sheets lookup) appears to be working fine & pulls the various formats for country.  I have the alpha-3 country code in the Keap connection to update the Billing Country but that's not being accepted on the Keap side.  Is that what is required for that field?  Attached is a screen shot of the field/data mapped to that field and what happens on the Keap contact record.
    In this example, the contact record also had full address data in there before the Zap updated the contacts record and you’ll see all the other address data all gets wiped-out (street 1, city, state, zip).  The country code also doesn’t map properly and shows an invalid value.  
    This all use to work & the Zap is now breaking our contact records by wiping out data...

thanks for your help!

You are most welcome, ​@Keap NH! 🤗

Is there #/area I can reference and monitor this bug progress?  Might we know when this will be fixed?

Bug reports are internal and not public facing—only Zapier and the Keap’s developers would have access to view the details and status of the bug report. We cannot provide any sort of estimate as to when their developers will be able to resolve this issue by but I’ll be sure to follow up here if I come across any workaround or updates on the status of the bug in the meantime. 

 

as for my second issue regarding Country Code integration to Keap contact records - the translator (google sheets lookup) appears to be working fine & pulls the various formats for country.  I have the alpha-3 country code in the Keap connection to update the Billing Country but that's not being accepted on the Keap side.  Is that what is required for that field?  Attached is a screen shot of the field/data mapped to that field and what happens on the Keap contact record.
In this example, the contact record also had full address data in there before the Zap updated the contacts record and you’ll see all the other address data all gets wiped-out (street 1, city, state, zip).  The country code also doesn’t map properly and shows an invalid value.  
This all use to work & the Zap is now breaking our contact records by wiping out data...

Hmm, I wonder if this could actually be linked to that same bug as well and it’s only showing the code as being invalid as the rest of the address is now missing:

8bc01727c263a1f65cab0132cb66cf7c.png

If you manually type in the rest of the address for that contact record in Keap does the country code still appear as USA (Invalid) or does it then appear correctly as just USA?

Reply


Terms & Conditions