Problem with Zapier APIs extracting Address REGION codes, and inability to set REGION during Create or Update Contact Zap

API Q&A
1

I am trying to set Contact Address fields in one Keap App, using contact data extracted from another Keap App using the ‘New Contact Tag applied’ trigger.

When setting REGION on the contact, the ‘Create or Update Contact’ zap requires the REGION CODE. I understand the reason for that. However, the trigger zap that outputs contact data, outputs the Region as a text field (e.g. “New South Wales”) not as the Region Code. This means I cannot update the contact’s address.

Furthermore, the REGION CODE includes the COUNTRY CODE. However for Australia, the COUNTRY CODE is “AUS” but the REGION CODE starts with “AU-” (e.g. “AU-NSW”).

How can this be resolved? Is it a limitation in the API calls not outputting REGION CODE? What if Address data is provided by a third-party database? Is there a (large) lookup table that can map all global Regions (text) to their Keap Region Code?

image
image1774×1056 208 KB

2

We cover this issues all the time.

You need to set up a step before adding data to Zapier that converts the data to the required output. I have a blog post that outlines it here: Keap (formerly Infusionsoft) Address Issues When Using API | 4Spot Consulting

Thanks,
Jeff

Jeff Arnold
4Spot Consulting • 4SpotConsulting.com
11700 W Charleston #170-160 • Las Vegas • NV • 89135
O: 702-721-9763 • C: 702-525-9763
Book an Appointment

For support related questions, please contact:
General Support: Support@4SpotConsulting.com
PastedGraphic-1

3

I ran into this same issue in Zapier. My solution (for now at least) was to CLONE an old Zap that was using the now unavailable Keap Max Classic tool (rather than the new Keap tool) and then just edit the cloned zap. You can’t create a NEW Zap with the Keap Max Classic option, but it WILL allow you to clone an old zap then use the Keap Max Classic tool in the cloned zap. The old Keap Max Classic tool uses the old mapping of State, Country, etc., and doesn’t care if there is a misspelling etc. whereas the new Keap tool will FAIL if the region_code and/or country_code are not used OR if they not formatted correctly. This is a big problem for sure since Keap/Zapier have forced use of the new tool …

1 Like
4

I agree with this 100%. I’ve had the same issues and Zapier is fully aware of the problem but has not updated the App nor mentioned it as a known issue in forums. I’ve spoken to other Keap members and have received similar issues with this.

I extensively tested the issue and reached out to the Keap Community for help.

Since I’ve heard from other Keap Users having this issue, it seems like this is something bigger than I can solve alone. Honestly, this is an active ticket for both Keap API Engineers and Zap Developers. However, I haven’t seen any updates or resolutions on this matter from either of the providers.

Here are my findings on where the errors occur:

  1. JavaScript lookup and replace ( Assistance from Paul Solok)
  2. Zapier Email Parser to new App directly
  3. WPForms with new Zapier App
  4. Gravity Forms with new Zapier App
  5. Google Sheet Lookup Table - Changing the form to a dropdown with the Alpha-2 codes for the region and the Alpha-3 codes for the Country (The test run didn’t work, and I was still working on a massive Alpha-2 code list as there isn’t one pre-made for all of what we need.)
  6. If you enter the full state name and country name, you will get the same error: the Billing Region Code is missing.
  7. Keap native Form—I tried to use this form, but it doesn’t have the best Spam filter.
  8. Keap Developer App - Direct API Connector - Still had the Billing Region Code Missing Error.

The full thread regarding this issue, which initially appeared in 2017, was resolved and resurfaced within the past few months. It could be a consequence, but Keap is also making many updates to bring Keap Ultimate to the fold. Invalid country code and region - What IS valid? - #5 by Ming_Zhang

IMG_7476
IMG_74761179×2556 246 KB

image
image1819×1819 1.07 MB

I’ve tried to either create a workaround or fix any error I may have had, but to no avail. Before finding your response, I posted to the Keap Community Groups, GitHub and the Keap Developer Forums to try and find answers. This seems to be an old issue once resolved, but has resurface since updates started.

I’ll continue to share more information if I receive any feedback. Thank you for posting this as I thought I was maybe the only one experiencing these errors.

1 Like