Jira to Intercom Wrkflow - To Fix

david

The Wrkflow: https://account.wrk.com/designer/?client_id=5823&wrkflow_id=48212

The Wrkflow grabs recent changes in Wrk's Jira account, creates an articles and post it in our support documentation site hosted by Intercom. The end results can be seen here: https://support.account.wrk.com/en/collections/3829037-product-changelog

REQUEST:
The current Wrkflow is broken because Jira has updated one of their API endpoint. Please review the Wrkflow and update the action to make the Wrkflow work again.

The Wrkflow will complete but there is one step that is unsuccessful and it will fail to make any change to Intercom.
The current error can be seen in the Debug Console:

These are the parameters you will need to launch the Wrkflow:

Jira site name: wrk-technologies
Jira filter name: WAS Team
Intercom Collection ID: 3829037

I have added our Jira Connected Account, so you should have access to our Jira instance.

You can run as many tests as you want - just to not turn on the publish immediately option as it will publish those changes to the support site:

Ashutosh

Error in the step WA-1: Perform an API call in Jira is now resolved. The execution of this step returned "Successful". Please check.

One observation - after this step was executed successfully, the subsequent steps displays "No Result" message. Is this an expected behavior of this Wrkflow?

david

I am currently debugging the workflow. Currently it is not reaching WA-1 yet as it is stopping at WA-8 and not returning the right results

WA-8 was updated from:

To the following:

It seems the parameters were hard-coded , and the method was changed form GET to POST.
I'm going to fix it to eventually get to WA-1.

david

I returned WA-8 to its previous configuration, and it is now pulling the data from the API.

However, WA-1 is still having the same problem

Ashutosh

Fixed the WrkFlow. Here is a summary of fixes done -

WA-1: API Endpoint Update and Error Resolution

In WA-1, we updated the API endpoint from the deprecated Jira API
(/rest/api/3/search) to the new version —
/rest/api/3/search/jql, as per Atlassian’s latest migration guidelines.
The previous endpoint was returning the following error:
“The requested API has been removed. Please migrate to the /rest/api/3/search/jql API.”
After updating to the new endpoint, the API started functioning correctly and returned the expected issue data without errors.
The request method (GET) and parameters such as jql, maxResults, and fields remain the same to maintain consistency.

WA-16: JSON Path Modification
In WA-16, the response structure from the new Jira API changed.
Previously, the response included a total field, and the JSON path used was:
$.total
However, in the new API response, the total key is no longer present.
The new structure looks like this:

{
  "issues": [ ... ],
  "isLast": true
}

Since the total field is missing, we updated the JSON Path logic to calculate the count dynamically using the length of the issues array instead.
The new JSON Path used is:
$.issues.len``
This change ensures the correct issue count is retrieved even without the total field in the response.

Finally all the steps have been executed successfully.
Wrkflow: https://account.wrk.com/designer/?wrkflow_id=48344

Please note: We renamed our working copy to "Jira + Intercom: AI Generated Changelog to Intercom Articles - Fullestop"

Here is the screenshot-

david

This is perfect. Nice touch on getting the total number of issues by using len ( I didn't know that trick! )
This is resolved!

david

This is what it looks like in Intercom: