Actions56
- Acquisition Actions
- Asset Actions
- Baseline Actions
- Case Actions
- InterACT Actions
- Organization Actions
- Repository Actions
- Task Actions
- Triage Rule Actions
- User Actions
Case → Create
AI-generatedOverview
This node operation creates a new case within the AIR system. It is useful for managing and organizing investigations or incidents by defining a case with specific attributes such as name, organization, owner, visibility, and assigned users. For example, a security team can create a case to track a cybersecurity incident, assign it to specific users, and set its visibility to either public within the organization or private to selected users.
Use Case Examples
- Creating a new case named 'Incident 2024-06' for the 'Finance' organization, assigning it to a specific user, and setting the visibility to 'Private to Users'.
- Creating a public case for an organization to allow all members to view and contribute to the case details.
Properties
| Name | Meaning |
|---|---|
| Case Name | The name of the case to be created, used to identify the case. |
| Organization | The organization under which the case is created. It can be selected from a list, by ID, or by name. |
| Owner User | The user who will own and be responsible for the case. Can be selected from a list, by ID, or by username. |
| Visibility | Defines who can see the case. Options are 'Public to Organization' or 'Private to Users'. |
| Assigned User IDs | A comma-separated list of user IDs assigned to the case. This is required if the case visibility is set to private. |
Output
JSON
id- The unique identifier of the created case.name- The name of the created case.organizationId- The ID of the organization the case belongs to.ownerUserId- The ID of the user who owns the case.visibility- The visibility setting of the case.assignedUserIds- List of user IDs assigned to the case, if any.
Dependencies
- Requires an API key credential for authentication with the AIR system.
Troubleshooting
- Ensure that the 'Case Name' is provided and is not empty, as it is required.
- Verify that the 'Organization' is correctly specified either by selecting from the list, entering valid IDs, or providing a valid name.
- If 'Visibility' is set to 'Private to Users', make sure to provide valid 'Assigned User IDs' as a comma-separated string.
- Check that the 'Owner User' is correctly specified and exists in the system.
- Common errors may include authentication failures due to invalid API credentials, missing required fields, or invalid user or organization IDs. Verify all inputs and credentials to resolve these issues.