Power Automate Integration: Flow fails with 502 error and non-JSON response from Jotform

Microsoft Power Automate cannot run flows integrated with Jotform. Error message is {

  "error": {

    "code": 502,

    "source": "flow-apim-unitedstates-002-westus-01.azure-apim.net",

    "clientRequestId": "f8bb0ff7-723c-41be-8106-10692b33c0a6",

    "message": "The response is not in a JSON format.",

    "innerError": "Cannot read server response."

  }

}

Hi Georgia,

Thanks for reaching out to Jotform Support. I'm an AI assistant here to assist you.

Let me help you with that:

The 502 message in Power Automate saying "The response is not in a JSON format" usually means that, when Power Automate calls Jotform, it is receiving an HTML/error page instead of the expected data. With Jotform’s current Power Automate connector, there are a few key points to check.

First, confirm the correct Jotform connector and trigger setup

1. Go to your Microsoft Power Automate Dashboard and open the flow that is failing.
2. Check the trigger at the top of the flow and make sure it is using the official Jotform (or Jotform Enterprise, if you are on Enterprise) connector with the trigger “When a Response Is Submitted (Jotform)”.
3. Edit the trigger and under its Parameters (or Advanced Parameters), verify that:
   • Form ID is set to the correct form.
   • Output Format is set to Plain text (this is generally the safest option for data extraction and avoids formatting issues).

Second, re‑authenticate and test the Jotform connection

1. Open the Jotform trigger card in your flow and look for the connection details.
2. Click on Sign in / Edit connection and log in again with your Jotform account to re‑authorize the connector.
3. Save the flow, then use Test in Power Automate and submit a fresh response to your form to see if the issue persists.

Third, check for possible 502 responses from Jotform

1. Review the run history of your flow in Power Automate and open a failed run.
2. Inspect the Jotform trigger/action step and look at the raw outputs or error details. A 502 from Jotform typically indicates a temporary issue such as high load, maintenance, or a network problem on the path between Power Automate and Jotform.
3. Wait a few minutes and run another test submission. Temporary 502 responses often clear on their own once load or connectivity stabilizes.

For reference, Jotform’s own 502 page describes the most likely causes as:

• The site may be experiencing excessive load.
• The server is down for maintenance.
• There may be a network problem.

Fourth, verify your overall integration flow

Here is the recommended way to build a Jotform → Power Automate flow so that responses are handled correctly:

A. Add and configure Jotform as the trigger

1. Log in to your Microsoft Power Automate Dashboard, then on the left menu, click on Create.
2. Under Start From Blank, click on Automated Cloud Flow.
3. In the Build an Automated Cloud Flow window:
   • Enter a Flow Name.
   • In Choose Your Flow’s Trigger, search for Jotform and select When a Response Is Submitted (Jotform).
4. Click on Create.
5. In the connection window, click on Sign In, log in with your Jotform account, and authorize Power Automate.
6. In the trigger’s Parameters:
   • Enable Advanced Parameters so you can see Form ID and Output Format.
   • Select the correct Form ID.
   • Set Output Format to Plain text (recommended).

B. Add and configure your action(s)

1. On the Flow Designer page, click the Plus icon under the Jotform trigger.
2. In Add an Action, search for your target app (for example, Excel (Business) or Google Sheets) and select the desired action (for example, Insert Row).
3. Sign in to that app when prompted and authorize the connection.
4. Configure the action’s parameters (file, worksheet, columns, etc.) and map them to the Jotform fields from the trigger output.
5. Save the flow and then use Test to submit a new form response and confirm everything runs without errors.

Fifth, check Microsoft’s own limits and configuration

Power Automate has its own limits and behaviors that can affect how responses are processed. You can review Microsoft’s documentation on Power Automate Limits and Configuration to ensure your flow is within their limits (for example, request size, timeout, and frequency).

If you can share a bit more detail about your current flow (for example, whether you are using the standard Jotform connector or Jotform Enterprise, and which action follows the trigger), we can help narrow down the exact point where Power Automate is seeing the non‑JSON response.

Let us know if you have any other questions.

Using standard Jotform connector and the action following the trigger is Insert Row in Google Sheets.

The trigger error is: The response is not in a JSON format.

Hi Georgia,

Let me help you with that:

From what you described, the issue is happening directly on the Jotform trigger in Power Automate (before the Google Sheets Insert Row action runs). In this case, the key is to make sure the trigger is configured exactly as required and then re-test the flow from scratch.

First, recheck the Jotform trigger configuration

1. Open your flow in the Microsoft Power Automate Dashboard.
2. Click on the trigger card that says When a Response Is Submitted (Jotform).
3. In the Parameters (or Parameters tab), make sure:
   • Advanced Parameters are enabled so you can see both Form ID and Output Format.
   • Form ID is set to the correct form.
   • Output Format is explicitly set to Plain text (this is recommended for most data extraction scenarios).
4. Close and save the trigger (for example, by using the Backward Arrow icon or clicking outside the window).

Second, re-authenticate the Jotform and Google Sheets connections

1. On the Jotform trigger card, check the connection and click on Sign In (or similar) to log in again and re-authorize Jotform.
2. On the Google Sheets Insert Row action, open the card and confirm the Google connection is valid; if needed, sign in again with your Google account.
3. In the Google Sheets action’s Parameters, verify that File, Worksheet, and the Advanced Parameters (column mappings) are all set correctly.

Third, re-save and test the flow from a clean run

1. Click on Save at the top right of the Flow Designer.
2. Click on Test in Power Automate.
3. Submit a new response to the connected Jotform form and see if the trigger now runs without the “response is not in a JSON format” issue.

If the issue persists, it’s also worth confirming that:

• You are using a work or school account in Power Automate (personal accounts are not supported).
• Your flow passes Power Automate’s own limits and configuration (request size, timeouts, etc.). You can review these in Microsoft’s documentation on Power Automate Limits and Configuration.

After we hear back from you with the result of these tests (especially whether a brand-new test submission still fails at the trigger), we’ll have a better idea of what’s going on and how to help.

Let us know if you have any other questions.

Troubleshooting did not work. Jotform trigger error is "The response is not in a JSON format."

Hi Georgia,

Let me help you with that:

Based on the available information, the supported setup for the standard Jotform connector in Power Automate is:

• Use When a Response Is Submitted (Jotform) as the trigger.
• In the trigger’s Parameters, enable Advanced Parameters, select the correct Form ID, and choose an Output Format (plain text is generally best for data extraction).
• Add your action (for example, Google Sheets → Insert Row), sign in, and map the columns under Advanced Parameters.

Since you’ve already followed the standard troubleshooting and the trigger itself still returns “The response is not in a JSON format”, there are no additional documented Jotform-side steps or limitations beyond:

1. Recreating the flow from scratch following the documented sequence:
   • Integrate your form with Microsoft Power Automate from Form Builder → Settings → Integrations → Microsoft Power Automate → Visit Microsoft Power Automate.
   • In Power Automate, Create → Automated Cloud Flow, select When a Response Is Submitted (Jotform), and configure Form ID and Output Format.
   • Add Google Sheets → Insert Row, sign in, and map fields.
2. Verifying your Microsoft side against their own requirements:
   • You are using a work or school account (personal accounts are not supported).
   • Your flow respects Power Automate limits and configuration (request size, timeouts, etc.), as described in Microsoft’s Limits and Configuration article.

There is no further documented Jotform configuration change that specifically addresses a persistent “response is not in a JSON format” error on the Power Automate trigger once the standard setup and re-creation of the flow have been done.

Let us know if you have any other questions.

Hi Georgia,

If you can provide us more details about the flow, involving Jotform, we can get a better idea of what's going on. The error you're getting, usually suggests the JSON is broken. A screenshot of the flow in PowerAutomate, of where the error is returned would be really helpful as well. Our guide on How to Post Screenshots to Our Help Center shows you how to take one.

Once we hear back from you, we'll be able to help you with this.

We have the same issue. Is it because there is a change from Jotform?

Hi ManyRivers,

I’ve gone ahead and moved your other question to a separate thread to keep things tidy, and someone from our Support Team will help you out with it here.

Let us know if you have any other questions.

Just sharing what I did to resolve mine. I had to delete the trigger in my flow and add a new one followed by remapping all of the JotForm values to my flow. not practical, but at least this is what we can do to momentarily resolve it and to get the flow back up and working again.