Actions85
- Alert Actions
- Asset Actions
- Case Actions
- Comment Actions
- Datastore File Actions
- Datastore Folder Actions
- Evidence Actions
- IOC Actions
- Manage Metadata Actions
- Module Actions
- Note Actions
- Note Group Actions
- Task Actions
- Timeline Actions
Task → Get Many
AI-generatedOverview
This node operation retrieves multiple Task records associated with a specified Case ID from the DFIR IRIS system. It is useful for scenarios where users need to fetch detailed task information related to a particular case, such as in digital forensics and incident response workflows. For example, a user can get all tasks linked to a case to review their status, assignees, and history.
Use Case Examples
- Fetch all tasks for a given case to monitor progress and updates.
- Retrieve specific fields of tasks to generate reports or dashboards.
Properties
| Name | Meaning |
|---|---|
| Case ID | The unique identifier of the case for which tasks are to be retrieved. This is a required numeric input. |
| Options | Additional options to customize the task retrieval, including whether to return the raw response, which fields to include or exclude in the output. |
Output
JSON
custom_attributes- Custom attributes of the task.id- Unique identifier of the task.modification_history- History of modifications made to the task.task_assignees- Users assigned to the task.task_case_id- Identifier of the case the task belongs to.task_close_date- Date when the task was closed.task_description- Description of the task.task_last_update- Timestamp of the last update to the task.task_open_date- Date when the task was opened.task_status_id- Status identifier of the task.task_tags- Tags associated with the task.task_title- Title of the task.task_userid_close- User ID who closed the task.task_userid_open- User ID who opened the task.task_userid_update- User ID who last updated the task.task_uuid- UUID of the task.
Dependencies
- DFIR IRIS API authentication
Troubleshooting
- Ensure the Case ID is valid and exists in the system to avoid empty or error responses.
- If the node returns an error related to authentication, verify that the API credentials are correctly configured and have the necessary permissions.
- When using the 'Return Fields' option, ensure the field names are correctly spelled and valid to prevent incomplete data or errors.