Unanswered

Jotform Trigger - 401 Error on 'ListFields' API operation

(1) Share

Report

Posted on by rorypatten

When in edit mode, clicking on any Jotfrom trigger on new or existing forms now displays the following error message in the left pane editor for the Jotform trigger:

"Failed to retrieve dynamic outputs. As a result, this operation's outputs might not be visible in subsequent actions. Error details: The dynamic operation request to API 'jotform' operation 'ListFields' failed with status code 'Unauthorized'. This may indicate invalid input parameters. Error response: { "message": "401 Unauthorized" }"

Seems to indicate an authentication issue with the Jotform API endpoint that allows the flow editor to obtain the field names for the Jotform.

After network inspection, I observed multiple requests failed to the Jotform API. However, the error message indicates 400 bad request:

"The request to API 'jotform' operation 'ListFields' has invalid inputs. Error details: The API operation 'ListFields' is missing required property 'formID'"

The request sent has no formID in the parameters so I am under assumption this is an internal change on PowerAutomate side that has broken it.

Has anyone else experienced this issue?

Thanks,

Rory

Categories:

Using connectors

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Michael E. Gernaey 53,335 Super User 2025 Season 2 on at

Like (1)

Report

Hi @rorypatten

No this would be a change on the jotform side. Microsoft does not, nor can it, randomly chance paying 3rd party hosted connectors.

How to Use Jotform Enterprise in Microsoft Power Automate

I would look and see if JotForm changed their implementation. I suggest trying it with PostMan. See if you get the exact same issue.

definitely from them.

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
rorypatten 11 on at

Like (0)

Report

Hi @FLMike

Thanks for your response.

The problem self-resolved a few hours later, and we know Jotform to be quite volatile so agreed this was a change on the Jotform side.

Thanks,

Rory

Was this reply helpful? Yes No