Hi @brandiwoodson 

You need to use the Get Tasks action first for a specific
You feed the output from Get Tasks into the input for Get a Task.

As you stated, a single request fires off multiple workflow instances. 
Perhaps you could save these workflow instances ID into SPO or SQL. 
When a Workflow Instance run, save the Workflow Instance ID to a central repository (SPO or SQL)
This will make it easier to collect all the workflow instances from a single resource point.
 

Hope that helps

Hi @brandiwoodson, @Garrett is correct you can use the Nintex task action to get the task ID. 
 

There is a method to getting the ID of a task inside of the same workflow. the below article explains how you can create a parallel branch to get all of the task information in the same workflow, the purpose of the article is to use that information to build a custom email with fancy buttons however if you don’t need that you can ignore those steps. 
 

Hi @brandiwoodson 

You need to use the Get Tasks action first for a specific
You feed the output from Get Tasks into the input for Get a Task.

 

As you stated, a single request fires off multiple workflow instances. 
Perhaps you could save these workflow instances ID into SPO or SQL. 
When a Workflow Instance run, save the Workflow Instance ID to a central repository (SPO or SQL)
This will make it easier to collect all the workflow instances from a single resource point.
 

Hope that helps

Yah this Is what we are currently doing but ideally having a way to pass a unique text ID by the customer to be stored for each task would be helpful so they can be grouped the way we need and filtered and returned back up and then also allow a filter on get tasks to filter by workflow name or workflow ID would be a lifesaver. The fact we have to manage tasks outside NAC is inconvenient when we should be able to just grab them from the system that already has them stored. 

Hi @brandiwoodson 
Did any of these replies solve your question? 

No, I’m aware of the task actions now but they don’t do what we need when trying to terminate a specific task ID, you have to loop several layers in to find a task and the filters don’t give you the ability to get what you need. If you are attempting for example to terminate one specific task on one instance, you can’t identify it. You can pull all active tasks but you have to go several layers in to fetch more details to get task ID and then you end up not having a way to pull the specific task unless you have all the recipients (assignees). So I gave up.