My Zapier Payment Triggers have not seemed to trigger for any Payments coming from our 5 Keap Accounts. The latest trigger from one of our accounts was on February 14th at 9:34 PM EST. When I use Zapier in Edit mode and attempt to retrieve payments manually to Test, payments come through from today, Feb 12th. That indicates to me that Zapier is still connected and can read data from Keap, but Keap is not triggering the step in the Zap (payment webhook?) Has something changed with the API or the Zapier integration to cause this and what solutions are there to potentially remedy this?
February 16th - not 12th.
Hi @Dev_FinMC,
Keap updated the API on February 14th to remove the old Legacy API Key. But it seems their change may have accidentally knocked out older OAuth Integrations that pass the Access Token via the URL Parameter.
Are you using the latest version of Zapier Keap integration, or an older version?
Looping in @Jeff_Arnold to see if he has been getting reports of this issue, and if he has a workaround.
Hi Pav,
I was using the Keap Max Classic version of the Zapier Integration, as the newest version does not seem to send the Pay Type (Credit Card, Credit, Refund) or the Invoice ID. We specifically rely on Credit Card and Refund Pay Types being labelled so we know who to remove from our products, and we use the Invoice ID for lookups (passing to AWS Lambda and using the XML-RPC API).
I thought the Legacy API Keys were disabled back in October when that notice went out. Was there some change to the date?
I was able to update the Legacy version of the Integration to a more Updated version of the Keap Max Classic integration, which seems to be working for now. With the missing info in the newest Integration it would require a significant reworking of our logic which we have not allotted time for currently.
Thanks!
@Dev_FinMC, the October 31st 2024 deadline was to get the integrations to pass the API Key via the HTTP Header. They allowed the Legacy API Key to be used until February 14th 2025. Although what Keap should have done was to get everyone to generate a New Service Account Key to replace their old Legacy API Key for October. A small number of people may have been caught out with this recent change.
I do not use Zapier when building integrations, given its limited scope on things. I would have assumed that the newer version of the Keap Integration would have been backward compatible. Seems it is a typical pattern with Keap lately, they introduce something new to replace the old, but leave out pieces of functionality.
The alternative to Zapier would be Make - https://www.make.com/en, but cannot guarantee if it would cover all your requirements. @Jeff_Arnold can give a better response on this.
Yes, we can capture that info using Make.
Email me if you’d like to chat about us possibly helping you with your buildout.
If you can handle it yourself, use the link I provided to get 10K free actions to try Make out.
Thanks,
Jeff
jeff@4spotconsulting.com