Hi, we have a WordPress website, and we are using the Gravity Forms Infusionsoft Plugin.
We’ve created a Developer Account and generated a new API key. Also we authorized the connection with Gravity Forms.
Could you please let us know if there’s anything else we need to do to ensure everything is ready before you implement the new functionality on October 31, 2024?
Hi @Richard_Bergman,
From your pictures I can see that Gravity Forms are supporting Authorized Connections (OAuth), which is all okay.
Have you checked all the other integrations that are connected to your Keap account are no longer using the Legacy API Key?
We’ve also updated the settings for the ‘Infusionsoft Account Information.’ Everything seems to be okay, but it’s hard to be certain. Could you let us know if there’s anything else we need to do?
@Richard_Bergman, I recommend that you remove your API Key and Account Subdomain from that section that you just posted.
Do you have to select which Infusionsoft Account you are using? I presume now that you added a second account that Gravity Forms will use that instead.
I see that we have two different add-ons/plugins with the same name.
The first plugin uses credentials from the Development Account (Link: https://keys.developer.keap.com/).
The second plugin uses credentials from the Keap website > Profile > API Settings (Link: https://keap.com/).
Could you please clarify which add-on/plugin is correct and will work after October 31st?
@Richard_Bergman, i am not a Gravity Forms expert, so I am not sure which instance of the Infusionsoft Plugin is taking control.
I recommend that you double check the Forms so they are connected to Infusionsoft Account #2, as shown in your first picture that you posted. That will carry on working after October 31st. Otherwise, you may end up losing the connection if you remove the Account with the Legacy API Key.
This is the Infusionsoft Plugin you need to remove below.
Ok, I’ll do that! Thank you so much for your help!
