Workflows for tasks

I have been investigating a similar use case. Completed tasks within the workflow would trigger additional actions within the workflow. Below is a semi step by step process for this

Using the powershell module with the following code will return Json data that can be used with the parser 

 

$APIKey = 'APIKEYHERE'
$EncodedCredentials = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(("{0}:{1}" -f $APIKey,$null)))
$Global:FSHTTPHeaders = @{}
$Global:FSHTTPHeaders.Add('Authorization', ("Basic {0}" -f $EncodedCredentials))
$Global:FSHTTPHeaders.Add('Content-Type', 'application/json')
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$URL = ("https://DOMAINHERE.freshservice.com/api/v2/tickets/TICKETNUMBERHERE/tasks")
$curl = Invoke-RestMethod -Method Get -Uri $URL -Headers $FSHTTPHeaders -UseBasicParsing
echo $curl | ConvertTo-Json # Uncomment here if needed -> -depth 5

in the parser it should look something like this

$.tasks1.status should return the first value in the array

1 = open status

2 = pending satus

3 = closed status


Using a similar syntax within the conditions module would allow check for status
 

Hello,

I appreciate your input on the need for standard nodes in the task module for workflow automation. It sounds like you encountered some limitations in your recent task automation, and having more standard nodes could provide greater flexibility and control.

Your suggestion makes sense, and I agree that it would be beneficial. I'll certainly vote in favor of adding these standard nodes to the task module, as it could streamline and improve workflow automation for many users.

Thank you for sharing your feedback and contributing to the community's discussion.

Best regards,Farrukh

And they have been :)