Skip to main content
Question

Jotform+Bloomerang Testing Error: Cannot convert undefined or null to object

  • Sep 24, 2026 3:27 PM UTC
  • 4 replies
  • 56 views

I am using Jotform as a trigger to Bloomerang. I submitted a test response to your Jotform before testing and am getting this error message:

Error code: Error while retrieving: Cannot convert undefined or null to object

Any ideas how to resolve this?

4 replies

SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • Sep 25, 2026 10:20 AM UTC

Hi ​@Michael Hansen, welcome to the Community! 👋

I can see you’ve reached out to our Support team about this as well, and they thought it may be related to HIPAA compliance. Sharing the steps they recommended here in case it helps others coming across the same Jotform error: 

The "Cannot convert undefined or null to object" error typically indicates that your Jotform connection in Zapier is set up with HIPAA enabled, but your Jotform account doesn't actually have HIPAA compliance turned on (HIPAA is only available on Jotform Gold or Enterprise plans). When there's a mismatch, Jotform's API returns empty submission data, causing the trigger to fail.
 
Here's what I recommend:

  1. First, confirm whether your Jotform account is actually HIPAA-compliant. You can check this in your Jotform settings.
     
  2. If HIPAA is NOT enabled on your account (most likely), you'll want to reconnect your Jotform account in Zapier:
    1. Go to Settings → Connected Accounts → Jotform
    2. Click Disconnect
    3. Reconnect and select "No" for both "Account HIPAA compliant?" and "European Data Centers"
    4. Then re-select your form in the trigger step and test again
       
  3. If HIPAA IS enabled on your account, check whether your form fields have the PHI (Protected Health Information) toggle turned on in Jotform's Form Builder. Fields with PHI enabled won't send data to Zapier. Toggle PHI to OFF for any fields you need in your Zap.

 

Let us know how it goes with those steps. Want to make sure this gets sorted! 🙂


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Sep 25, 2026 6:25 PM UTC

Hi ​@Michael Hansen 

For us to have more context, post screenshots showing:

  • how your Zap steps are outlined
  • how your Zap steps are configured
  • the encountered error in the Zap step

SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • Oct 20, 2026 10:19 AM UTC

Hey ​@Michael Hansen! How did things go with the steps the Support team suggested? Did that sort it, or is it still erroring?


Forum|alt.badge.img+1

Hey ​@Michael Hansen Did you get the chance trying above suggestions and let us know if issue still persist.

  1. In Zapier, go to Connections, remove the JotForm connection, and add it again.
  2. When prompted, set HIPAA compliance to No (unless your JotForm plan is genuinely HIPAA-enabled). Set the EU data center option to match your account.
  3. In JotForm, turn off Encrypt Form Data (Form Builder → Settings).
  4. In JotForm, turn off Require Log-in to View Uploaded Files (Profile → Settings → Security → Privacy).
  5. Confirm the JotForm account connected in Zapier owns the form you're using.

If it still fails: this is a known open issue, so use the workaround. Turn the Zap on, submit a new live entry to the form, and map the fields from the live run data instead of the test sample.