I have 2 cards so far on a workflow with the 1st being an on demand API endpoint. The get multiple is set with the object = body from the API endpoint card. Errors sometimes are shown on the get multiple card and it consistently seems to be related to having literally new lines in the JSON body.
The error. Invalid type conversion: Cannot parse string character (\m0000-\u001F) found while parsing a string at line 9 column 0.
Example body: {
“eventType”: “jira:issue_created:issue_created”,
“timestamp”: “2025-08-26T20:10:46.7+0000”,
“issue”: {
“key”: “AISD-383”,
“id”: “34705”,
“summary”: “Request for dedicated GPU access”,
“description”: "Hi Team, Could you help reserve a GPU under z lab account? If cpu needs to be specify, it could be 32 cpus with 4G mem each. Let me know what other information you need.
The JSON object returned varies. I’m thinking of replacing the 2nd card with a Get card with the path eventType. Then use If/Else given the event type. But I’ll still need to get the description from the body if it exists in the JSON. See sample in the original post
{
"eventType": "jira:issue_created:issue_created",
"timestamp": "2025-08-26T20:10:46.7+0000",
"issue": {
"key": "AISD-383",
"id": "34705",
"summary": "Request for dedicated GPU access",
"description": "Hi Team, Could you help reserve a GPU under abc lab account? If cpu needs to be specify, it could be 32 cpus with 4G mem each. Let me know what other information you need.\n\nThanks,\n\nJane",
"issueType": "[System] Service request",
"priority": "High",
"status": "Waiting for support",
"statusId": "10127",
"statusCategory": "In Progress",
"project": {
"key": "AISD",
"name": "HPC Service Desk: Arc Institute"
},
"reporter": {
"displayName": "Jane Summers",
"emailAddress": "summers.jane@company.com"
},
"created": "2025-08-26T20:10:44.8+0000"
},
"serviceDesk": {
"requestType": "",
"customerEmail": "",
"customerName": ""
}
}
Which key do you need to extract?
Also, in this picture, the ‘object’ in the Get Multiple card is blank. What do you pass there? Can you show the flow in the design view?
I think the issue is with the incoming data… for instance, if I copy paste the text that @rcortez provided, I also get an error trying to parse it.
If I copy/paste the text you provided, it works.
I’m not sure what you mean by the keys… there are lots of them… “issueType”, “priority”, “status”, “description”, etc.
@rcortez - you will probably want to build a handler like you mentioned so that you are grabbing the right keys depending on the request that’s being made. In your example, there isn’t ‘comment.body’ or data for most of the fields you selected.
I think that usually shouldn’t really be an issue and those fields should just return a null if we can’t find anything and are able to parse the data correctly, but it can still be helpful to be able to easily trace which types of requests came into the flow, etc.
I think there’s just data coming in that it doesn’t like…
JSON requires control characters in strings to be escaped. RFC 4627
> section 2.5:
>
> A string begins and ends with quotation marks. All Unicode
> characters may be placed within the quotation marks except for the
> characters that must be escaped: quotation mark, reverse solidus, and
> the control characters (U+0000 through U+001F).
>
@rcortez I’d maybe see if you can fix the formatting issues on the JIRA side, seems like it might be related to the new lines not being escaped or some other value in the JSON in your one example.
I agree. This is probably better solved on the Jira side, with the admin, when they’re available. I believe the JSON is triggered from an automation with a Send Web Request.
The automation can be set with a Data Format, Jira or Automation. Documentation I’ve found states Jira format will replace the blank lines with \n
The keys can be adjusted on my side.
Thanks to you both. It helps to get other viewpoints.
Solved. The Jira automation had the data format set Custom. The idea was to have a small JSON package in the response. The automations are now set with Jira format. \n replaces the blank lines.
