I was wondering if anyone knew where I could find information on the difference between Keap (Classic) Steps in Zapier and what I assume is the more up-to-date version of those steps. I noticed in the main thread about the Legacy API sunsetting that Zapier Keap steps should not be affected, but I want to be sure my team is prepared ahead of time if there will eventually be any effect there or if Keap (Classic) Steps themselves have some eventual end date.
The answer depends on how long ago you set up Zapier with Keap?
I would say that the majority of people would be using the authorised their Keap Connection with Zapier. But, I recently came across someone who was using Zapier against the original Legacy API Key. They are migrating their Zaps from the older Infusionsoft version to the newer Keap Zap (Not Keap Max Classic).
I recommend that you ask Keap Support for a report on your Keap Account Legacy API Key usage. In that report you will see if you have any Zapier Keap Zaps running off the Legacy API Key. It will just say “Zapier” in the User Agent. If there is none in there, then you are okay.
Apart from Zapier, do you have any other Keap Integrations that were set up using the Legacy API Key? I recommend that you review those as well.
So the Zap Connections were made relatively recently and are using the Steps within Zapier themselves - using a non-Legacy Key. I will double-check with Support to confirm I am not missing any. I just noticed that the Steps technically say Classic and that there are newer versions of those Steps, but I was having some issues finding comparable functionality for a few things we are relying on.
As far as other Integrations with Keap, we do/did have some using Legacy Keys, but another Developer has handled the conversion and we should be all set there. Again, I will loop back with her once I get information from Support, if there is still usage noted.
Sorry for the tardy delay … was out on vacation.
As Pav mentioned, I’m a Zapier Certified Expert, but we’ve been transitioning our client to Make, as it is easier to use and is FAR less expensive. (It’s backed by a 12B company, so it’s not just a rando piece of software someone hacked together). May be worth a look if you are having difficulty finding the items you need in Zapier.
I’m glad you found your solution. I’ll keep monitoring the space for furture questions.
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
No worries Jeff and thanks for the recommendation.
I did actually have a related question that you may be able to give me insight on, since I am still using Zapier currently.
So I was previously using a Code Step to make calls to the Keap REST API, because it gave me more flexibility than Zap Steps do. I was using the endpoint for Orders, but passing in the Invoice ID from the Payment Trigger, since the REST API does not seem to have an Invoice lookup. I have 3 accounts where this works - either through the REST API endpoint, or the Zap Step for Keap Invoice ID lookup. However, I have 2 other accounts where using that ID either through the Retrieve an Order endpoint or the Invoice ID lookup Zap Step continually fails to find the Invoice.
Am I misunderstanding how these are related or are supposed to work? Any advice would be excellent.
@Dev_FinMC, I need to point that the Order and Invoice ID Numbers may not always be in Sync. Depending what activity that has been done over the years, it is possible for the Numbers to be either 2 or more digits apart. That can be annoying when you have to look up things.
The REST API is too limiting in places, whereas the XML-RPC API offers better querying flexibility. I know that the latter is not preferred anymore, but Keap are not doing enough to improve the REST API experience.
As for the Zap failures, I will let @Jeff_Arnold pass his thoughts onto this.
As Pav mentioned, the issue may be with the ID you are searching for. the invoice vs Order Id issue is very frustrating, as we’ve worked with clients who had their numbering offset by 4 (order 10 was invoice 14, etc), so if you are using order 10 and trying to pull invoice 10, you may get an error.
Other than that, if you are using the same call but for different accounts and it isn’t working, I wouldn’t have any idea of why you would be getting those various results.