InfusionSoft Integration: HIPAA Account using InfusionSoft Integration, no contacts being added

  • Profile Image
    Asked on August 23, 2018 at 01:06 PM

    Hello, I'm currently trying to make an integration with InfusionSoft. I've made a simple campaign that adds a tag to the contact when they're added by the integration. I've made sure to use a goal name that matches what I wrote in the integration. However, a contact is never added. The current HIPAA form I'm using to test this is

    I've tried reducing the number of fields I'm giving to infusionsoft as well as making a simpler campaign.

    Also, a heads up, when you authenticate infusionsoft with a hipaa jotform account, it automatically sends you to a www.jotform URL, which makes the request fail, but if the URL is changed to hipaa.jotform, the authentication request goes through.

  • Profile Image
    Answered on August 23, 2018 at 02:06 PM

    I have cloned your form and tested it. It works well on my end.

    Could you please give us more details so we can replicate your steps.

  • Profile Image
    Answered on August 23, 2018 at 02:14 PM

     Sure, I'll attach some screenshots.1535047881Screen Shot 2018-08-23 at 1.09

    Here's how I mapped out some of the fields on the jotform integration side.

    1535047967Screen Shot 2018-08-23 at 1.09

    setting api call name

    1535047988Screen Shot 2018-08-23 at 1.10

    Infusionsoft side

    1535048016Screen Shot 2018-08-23 at 1.10

    Simple sequence within campaign that adds tag.

    Also, while I was gathering these screenshots, it said the refresh token wasn't valid so I had to re-authenticate each time I edited the integration.

  • Profile Image
    Answered on August 23, 2018 at 03:24 PM

    I would recommend you to first make sure that your form sends the data to InfusionSoft, please try re-integrating your form, this should clear up any issue with the current one. 

    Once you've re-integrated, please just map a few fields and test the integration, once you've noticed the records are generated in InfusionSoft, try setting up the goal.

    To integrate JotForm with InfusionSoft, please follow these steps: 

    1. Edit your form on the form builder, and go to the settings tab, integrations section and scroll a bit down to find the InfusionSoft app: 


    2. Once you click on the integration, you will need to authenticate:


    You will get a pop-up window where you will need to log in into your InfusionSoft account: 


    3. Once you have logged in, you will get the integration settings.

    - Match the fields from your form to your InfusionSoft application, please make sure you map the same field types in order to avoid issues sending the submitted data to the app:


    - The tags from your InfusionSoft app will be loaded as well so you can select those ones that will be applied to the records added from JotForm: 


    - Actions will also be loaded so you can apply any to the records added from JotForm: 


    First, try to follow the above steps and ensure that the leads are going to your InfusionSoft account. If it is successful then try to create the campaign goals

    To achieve campaign goals please check this guide: 

    If you have any question, please let us know.


  • Profile Image
    Answered on August 23, 2018 at 03:33 PM

    Yes that's how I originally integrated it.

    For me it pulls up a new tab in infusionsoft and asks me to select an account (since I'm already logged in)

    1535052630Screen Shot 2018-08-23 at 2.29

    However, when I click allow I get sent to

    This page is blank except for a plain text "200" which I assume refers to the HTTP Code of the page. If I change the www subdomain to hipaa, the tab auto closes and now the integration says it's authenticated. After redoing the integration following the steps above, it still does not add contacts to my infusionsoft account.

  • Profile Image
    Answered on August 23, 2018 at 04:21 PM

    These are my settings:

    InfusionSoft side setting is the default, no Campaign Goals.

    I suggest you do the same and see how it goes.

  • Profile Image
    Answered on August 23, 2018 at 04:32 PM

    Alright, I removed the API Call Name, the fields were already matched as described above. Also did default settings on the infusionsoft side. I submitted a form just now and it didn't show on infusionsoft contacts. Does it have anything to do with the fact that it's a HIPAA form? 

  • Profile Image
    Answered on August 23, 2018 at 04:59 PM

    As a long shot I tried making the fields I was sending to infusionsoft not protected fields, but that didn't change anything.

  • Profile Image
    Answered on August 23, 2018 at 05:34 PM

    Hey, just an update. I have this same form in a non HIPAA format on another account. I made the integration again on the non HIPAA form, and it works as intended. So, I figure something is going wrong with how HIPAA jotforms communicate with InfusionSoft

  • Profile Image
    Answered on August 23, 2018 at 07:46 PM

    Can you please confirm first if your Infusionsoft account was successfully authenticated during the integration setup on the HIPAA enabled account?

    You can do this by removing first the integration and redo the process. Try opening an incognito or private browser and log in to your JotForm.

    If the authentication window shows that you are already logged in to Infusionsoft, try log out first.

    1535067951zzz 2018-08-24 07.44.21.png

    the redo the authentication steps

  • Profile Image
    Answered on August 24, 2018 at 10:49 AM

    Just tried that. The same window appears when I log back in to InfusionSoft, I select the account and press allow, and it takes me to

    1535121814Screen Shot 2018-08-24 at 9.43

    This is the page it takes me to.

    Below is the console of said page when I inspect it.

    1535121896Screen Shot 2018-08-24 at 9.43

    Here's the output in plain text: "DOMException: Blocked a frame with origin "" from accessing a cross-origin frame.

        at "

    I figured it's because the request is coming from a hipaa subdomain while this is on www subdomain, so when I replace www with hipaa the authentication goes through. I'm going to try out one more thing, but yes, it still doesn't not go through to infusionsoft.

  • Profile Image
    Answered on August 24, 2018 at 12:15 PM

    I was able to replicate this. I will send this thread to our development team to look further into this issue.

    You will be updated on the progress as soon as possible.


  • Profile Image
    Answered on August 28, 2018 at 11:55 AM

    Hello, are there any updates on this? My company is relying on this integration to pass along HIPAA compliant data.

  • Profile Image
    Answered on August 28, 2018 at 12:46 PM

    There is no update on this right now but I see that this thread is marked as important and on the priority list of our development team. You would be updated ASAP.

    We appreciate your patience.


  • Profile Image
    Answered on September 12, 2018 at 10:39 AM

    Hey, just an update. We talked to infusionsoft and it seems that there's a field in the access token request to Infusionsoft that specifies the redirect url. The redirect_url field should dynamically change to a URL when the form involved in the integration is on a HIPAA account.

    Here's what they said:

    "My name is Wyatt, and I'm with the developer support team at Infusionsoft. This email is regarding the HIPAA integration with JotForm. Sadly, there isn't anything that we're able to do on our side of things. The redirect is set up in the call that they make to us when retrieving their access_token. That is ultimately what lets the access_token and refresh_token get passed back to their servers. 

    They should be able to create a "forked" version of their code (essentially an independent copy) and then find/replace the redirect_url in those requests. But, that all depends on what type of environment they are currently working in."
  • Profile Image
    Answered on September 12, 2018 at 11:31 AM

    Thank you for the additional details. We'll pass this on to our development team too.