Fusion Parse JSON error message

[OmahaOmaha]

Has anyone received the following error message after running a GET api call?

DataError

Source is not valid JSON.

Origin

Workfront Fusion

• Bundle 1Collection
  • JSON string
    {[Collection],[Collection],200}

I was able to get all of the fields I needed from the parse json module into my set variables module when setting up the scenario, but when I run it, it doesn't work.

[NathanJo1 · Accepted solution]

Hi @OmahaOmaha 

This is something we have seen before in support. The error "DataError: Source is not valid JSON" in Workfront Fusion usually occurs when a GET API call returns a response that isn’t valid JSON. This often happens if the API endpoint returns HTML (such as a login page or an error message) instead of the expected JSON data—commonly due to authentication issues, expired tokens, or incorrect endpoints. Fusion modules like Parse JSON expect valid JSON, so if the response is malformed or in an unexpected format (e.g., an array when an object is expected), the scenario fails.

To troubleshoot, review the execution log and inspect the raw output from the HTTP request module. If the response starts with HTML tags or contains error text, check your authentication and endpoint configuration. Validate the response format using a JSON validator. Adjust the scenario configuration to handle arrays or empty responses as needed.

If the API consistently returns non-JSON data, please submit a case to support.

Thanks,
Nathan

[tusharac]

try some JSON validator like https://validatejson.com 

[kautuk_sahni]

@OmahaOmaha Just checking in — were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!